Jakarta EE namespace transition

[jGauravGupta]

Signed-off-by: Gaurav Gupta [email protected]

[rdebusscher]

Looks good.

There are a few other name changes required (like those for Jakarta Authorizaiton and Jakarta Authentication), but that can be done in another PR.

[arjantijms]

Thanks @jGauravGupta !

[keilw]

@arjantijms So this Jakarta spec will use "jakarta.security.enterprise", what about the other two raised e.g. by @thodorisbais?

[arjantijms]

@keilw

This concerns the implementation. I wonder whether the artefact id should not just be "soteria" in stead of "jakarta.security.enterprise".

For the API though it should probably just be "jakarta.security". The "enterprise" part is unneeded. See here: https://github.com/eclipse-ee4j/security-api/blob/master/api/pom.xml#L30

[keilw]

Indeed, in the "impl" module "jakarta.security.enterprise" feels completely wrong, but I also spotted a few other problems, I'll raise a PR for that.
Regarding the API if we drop the "enterprise" that sounds fine, the question for all of them remains, if the Java packages of each API correspond with that groupId or not?

[arjantijms]

It’s a small pattern that made a little sense for the RIs in Java EE:

Javax.foo and Javax.foo-api

But even there it wasn’t done consistently. Updated Java packages can be considered for Jakarta EE 10 yes. A bunch of people also asked to make Authentication and Authorization sub-specs of Security, we might look into that too then.

[keilw]

If the refactoring doesn't break anything later in Jakarta EE 10, we might do that later. Ideally the artifactId should only be changed once e.g. now after the specs got new names like "Authorization".