| Re: [jakartaee-platform-dev] [jakarta.ee-spec.committee] JakartaSecurity Spec Namespace Mismatch |
Kevin, Thanks, it already exists https://github.com/eclipse-ee4j/authentication/issues/89 However, the API package is currently "jakarta.security.auth.message", I mentioned on different occasions, that simply renaming "javax" to "jakarta" is not always the proper solution, at least in this case it creates lots of confusion unless the Java packages were also renamed to match the project/spec name. https://github.com/eclipse-ee4j/authorization/issues/68 also exists for Authorization. There it is also equally complex, the Java package is just named "jakarta.security.jacc", the groupId "jakarta.authorization", so IMO both would have to change for a proper match. Werner Sent from Mail for Windows 10 From: Kevin Sutter Werner,
Hi,
I recently noticed, that renaming some specs like JASPIC to another Jakarta name had a side-effect of a mismatch and inconsistency of the Maven GroupIds.
While Jakarta Autorization (https://github.com/eclipse-ee4j/authorization) ended up with: <groupId>jakarta.authorization</groupId> <artifactId>jakarta.authorization-api</artifactId>
Its sibling Jakarta Authorization (https://github.com/eclipse-ee4j/authentication) sticks with a GroupId root already known by Jakarta Security: <groupId>jakarta.security.auth.message</groupId> <artifactId>jakarta.security.auth.message-api</artifactId>
Was there a reason to abandon the "jakarta.security" prefix for one, but keep it for the other?
Also IMO "jakarta.security.auth.message" is wrong on so many levels, to start with it confuses people with Jakarta Messaging because the word "message" and the acronym "auth" tells nothing whether it is "authorization" or "authentication".
Since they were both recently changed from the "javax" namespace, I doubt either of them are "given by God" now, so could we at least harmonize them, either with the "jakarta.security" prefix or without?
Thanks, Werner _______________________________________________ |
