Hi, If there’s no real value in the "security" package layer (again it seemed also to differentiate from Java SE packages like "javax.security.auth" or "javax.security.cert" and it seems they are intended to stay in Java SE for some time?) then a ++1 from me to "jakarta.authentication" "jakarta.authorization" "jakarta.security" Werner If we/you strictly obey to the https://wiki.eclipse.org/JakartaEE_Maven_Versioning_Rules, Then <groupId>${API_PACKAGE}</groupId> would mean having to keep the package level "jakarta.security" for all specs that reside there. So unless the Java package of Jakarta Authorization was going to abandon the "security", the Jakarta Authorization group id should be "jakarta.security.authorization" and not just "jakarta.authorization".
Currently the package is jakarta.security.jacc, and so was the group id before, but we had to move to something else as mentioned because of the version issue. I'm not exactly sure what the rules are for changing packages post Jakarta EE 9. I'd be in favour of keeping every small, although without abbreviations. Project: Jakarta Faces, package: jakarta.faces, group id: jakarta.faces Project Jakarta Authentication, package jakarta.authentication, group id: jakarta.authentication Project Jakarta Authorization, package jakarta.authorization, group id: jakarta.authorization Project Jakarta Security, package jakarta.security, group id: jakarta.security Kind Regards, Werner Was there a reason to abandon the "jakarta.security" prefix for one, but keep it for the other?
Jakarta Authorization HAD to move to a new group id since there was a version mismatch between the spec and the last released jar. So this gave us the opportunity to come up with a fitting (better) group id. 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".
It's a confusing id indeed. I understand where they were coming from at the time, with "message" relating to (mainly) SOAP's distinction between Message Level Security (MLS) and Transport Level Security (TLS). Since at the time SOAP was the big hype (kinda like MicroServices are today), many things were named after SOAP concepts. At least, that's how I understood it. I'd love to see just jakarta.authentication as group id. If the PMC agrees and other stakeholders agree, it would be good to have this changed for Jakarta EE 9. 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
_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee
_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee |
