Make Maven coordinates consistent with rest of EE

[arjantijms]

CDI has one of the most inconsistent Maven coordinates currently.

Most every API in Jakarta EE has jakarta.[spec name]:jakarta.[spec name]-api.

Where "spec name" is written fully if its a simple single word name, or using an abbreviation if its multiple words:

E.g.

• jakarta.ejb:jakarta.ejb-api
• jakarta.interceptor:jakarta.interceptor-api
• jakarta.servlet:jakarta.servlet-api
• jakarta.activation:jakarta.activation-api
• jakarta.mail:jakarta.mail-api
• jakarta.transaction:jakarta.transaction-api
• jakarta.el:jakarta.el-api
• ..

CDI however uses jakarta.enterprise:jakarta.enterprise.cdi-api

I propose using jakarta.cdi:jakarta.cdi-api.

cc @keilw @JanWesterkamp-iJUG @ivargrimstad

[Ladicek]

I think this makes sense.

[manovotn]

I always found the artifact name bamboozling myself.
I am not even sure how we landed on it after migrating to Jakarta :)

[manovotn]

In the CDI call today we agreed that we'd love to make this happen for 5.0 release (M2).

The question is, do we need to make any additional changes to be able to release under the new package name?
I suppose Sonatype will complain on release due to namespace and we'd need to add a new one but I have no idea who to contact to solve that - any ideas @ivargrimstad @arjantijms ?

[ivargrimstad]

File a help desk ticket in Gitlab

https://gitlab.eclipse.org/eclipsefdn/

[arjantijms]

Additionally, if needed, you can see how Jakarta Concurrency is preparing a similar move:

jakartaee/concurrency#555 which includes instructions how to do a redirect for Maven from the old to the new coordinates in their web UI.

[manovotn]

File a help desk ticket in Gitlab

https://gitlab.eclipse.org/eclipsefdn/

Thank you, I have created https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/6865

[manovotn]

FTR, we should now have the needed permission for CI bot to push under the new namespace.
See https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/6865#note_5324038

[manovotn]

After some additional struggle with repo config and Jenkins, I have managed to get 5.0.0.Alpha3 out that should contains:

• All the artifacts with changed coordinates
• Relocation artifacts with the old ones

Tomorrow I'll do a TCK release to make sure everything if working there as well but that should be way easier as we have no relocation there.