Re: [jakarta.ee-spec.committee] Jakarta Security Spec Namespace Mismatch

["Kevin Sutter" <sutter@xxxxxxxxxx>]

Werner,
Here's a pointer
to our Jakarta EE naming conventions:  https://wiki.eclipse.org/JakartaEE_Maven_Versioning_Rules

This would indicate
that Authentication should follow suit and change the groupId and artifactId
to be consistent.  Why don't you go ahead and write an Issue for this?
 Thanks!

---------------------------------------------------
Kevin Sutter 
STSM, MicroProfile and Jakarta EE architect @ IBM
e-mail:  sutter@xxxxxxxxxx     Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    
LinkedIn: https://www.linkedin.com/in/kevinwsutter



From:
       Werner
Keil <werner.keil@xxxxxxx>
To:
       jakartaee-platform
developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Cc:
       Jakarta
specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx>
Date:
       02/17/2020
12:42
Subject:
       [EXTERNAL]
[jakarta.ee-spec.committee] Jakarta Security Spec Namespace Mismatch
Sent
by:        jakarta.ee-spec.committee-bounces@xxxxxxxxxxx

---

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

 _______________________________________________
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