For the reasons Ivar outlined, I prefer option 1.
Plus there are multiple compatible implementations like EclipseLink or JNoSQL also in the "org.eclipse.something" namespace.
Which makes part of the upstream spec also sharing the same "org.eclipse.something" namespace a bad design smell on top of the namespace dilution and inconsistency of the platform.
When I voted earlier for my second choice, the case-by-case basis was the only alternative I saw, but IMO the gradual migration to the Jakarta namespace after an initial start with the original namespace is my second choice (alternative 2 I think, not 1)
Werner
From: jakarta.ee-spec.committee <jakarta.ee-spec.committee-bounces@xxxxxxxxxxx> on behalf of Ed Bratt via jakarta.ee-spec.committee <jakarta.ee-spec.committee@xxxxxxxxxxx>
Sent: Wednesday, July 23, 2025 6:09 PM
To: Jakarta specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx>
Cc: Ed Bratt <ed.bratt@xxxxxxxxxx>
Subject: Re: [jakarta.ee-spec.committee] [External] : [Straw poll] namespace policy for existing specifications moving to the Jakarta specification project
For Oracle, we prefer Option 2
I have recorded this on the meeting agenda for today.
-- Ed Bratt
On 7/10/2025 9:12 AM, Thomas Watson via jakarta.ee-spec.committee wrote:
As discussed at the July 9th meeting, we decided to do a straw poll to determine the specification committee group's opinion on package namespaces used by specifications wanting to move to the Jakarta specification project.
Please respond to this straw poll by July 23, 2025 so we can discuss results at the next specification committee meeting.
For existing specification projects that wish to move to the Jakarta specification project select one of the following options:
option 1: Force the existing specification projects to move all of their API package namespaces to jakarta when they move to the Jakarta specification project
option 2: Allow existing specification projects to retain their own existing package namespaces when they move to the Jakarta specification project
option 3: no preference
Tom Watson
_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To unsubscribe from this list, visit https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee__;!!ACWV5N9M2RV99hQ!MYKAwexhTJ45WWAxkMo_-H13G9XbCNJnHP6SiEeSY1rxEe1O9dhYUIo64To6M9WiU2tLLNGY0XQDdPRdbLyGewDOABA$
|