Do we keep the "enterprise" in the groupId?

[keilw]

While this API has been a little more consistent than Authorization or Authentication, shall we keep the groupId "jakarta.security.enterprise" or change it to "jakarta.security"?

[arjantijms]

I'm +1 for "jakarta.security", mostly because the group id should IMHO as much as possible resemble the project name.

Since the project name is "Jakarta Security" and not "Jakarta Security Enterprise", frankly "jakarta.security" is the only right group id.

I do like to hear what the other committers think.

[keilw]

Ok would the fact, we already deploy to "jakarta.security" make it easier here with Sonatype or does that require another ticket with Eclipse Bugzilla or its tracking system?

[keilw]

I understood Sonatype does not distinguish subfolders of a top level groupId, but maybe something changed?

[rdebusscher]

Fine for dropping 'security'. But we should use the <relocation> so that transition becomes easier?

EDIT: I'm a sleep, of course I meant enterprise :)

[arjantijms]

Ok would the fact, we already deploy to "jakarta.security" make it easier here with Sonatype or does that require another ticket with Eclipse Bugzilla or its tracking system?

Not sure, but I can try to just stage, see what happens ;)

[keilw]

@rdebusscher No "enterprise" if anything to drop.

[ggam]

+1 for "jakarta.security"!

…

On Tue, May 26, 2020 at 11:59 AM Werner Keil ***@***.***> wrote: @rdebusscher <https://github.com/rdebusscher> No "enterprise" if anything to drop. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#169 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAQC44FQESRFSSZ6PWLR33DRTOHJFANCNFSM4NKDOPHA> .

[keilw]

As I asked the question, I would also go
+1 for "jakarta.security".

[arjantijms]

@rdebusscher No "enterprise" if anything to drop.

I think @rdebusscher made a typo there, as "jakarta.enterprise" would be a bit weird for the Jakarta Security project :P

[arjantijms]

Let's do this as one of the first things after 2.0 is released.

[keilw]

I think for now also similar in the other security specs the package names and module names are aligned somehow, so it may be for a future version to change all of them.

[keilw]

So "2.Next" would be 3.0 now aiming at Jakarta EE 10?

[arjantijms]

Yes, 2.next is now 3.0 ;)

[hantsy]

+1 for "jakarta.security".

It is better to remove the enterprise in other spec together as planned in a Jakarta stage, such as CDI, etc.