Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [microprofile-wg] [Straw Poll] [DISCUSSION] MicroProfile -> Jakarta EE - deciding namespace after the move

Hi Emily,

The problem with this poll is that it's not clear whether the org.eclipse.microprofile.* namespace can be kept without changing the Jakarta EE Specification Process (https://jakarta.ee/about/jesp/). Although the process mentions only that javax has to be changed to jakarta, and that jakarta namespace cannot be used for non-API artifacts, it was written under the assumption that all then-current Jakarta specifications came from Java EE. The JESP doesn't explicitly say anything about new specifications, but this might not be intentional and it should be clarified whether it's OK to release a Jakarta specification with a different namespace than jakarta.* to avoid confusion.

Ondro

On Mon, Jun 2, 2025 at 12:38 PM Emily Jiang via microprofile-wg <microprofile-wg@xxxxxxxxxxx> wrote:
Michael,
Thanks for your feedback! This straw poll is trying to say:
Move the MicroProfile specifications as they were and the namespace discussion can happen after the move and be decided by the comitters of the corresponding MicroProfile specification. 

Question: what namespace should be used for the moved MicroProfile Fault Tolerance.

Answer: it will be decided by the committers in MicroProfile Fault Tolerance. If the committers decide to keep the existing org.eclipse.microprofile.fault.tolerance, it is fine. However, if they want to change to jakarta.microprofile.fault.tolerance, it is fine too.

By the way, I need a bit more clarification regarding free-for-all. I don't understand your question either. Can you explain in more detail?
Thanks,
Emily

On Thu, May 29, 2025 at 11:39 AM Michael Redlich <mpredli@xxxxxxxxx> wrote:
-1 from the Garden State JUG.

Based on our interpretation of this straw poll, it sounds like there is the potential for a "free-for-all" in a naming convention.  Will the standard root namespace be required as it should?  This was not made clear, so we stand by our -1 with the way this has been written.



On Wed, May 28, 2025 at 12:53 PM Emily Jiang via microprofile-wg <microprofile-wg@xxxxxxxxxxx> wrote:


This is a non-binding straw poll vote-only thread, detailed below.  Anyone can vote. The working group member reps will be counted separately for the corresponding ballot projection. Please respond with +1 (positive), 0 (abstain), or -1 (reject).  Any feedback that you can provide to support your vote will be appreciated.  Please respond by June 4th, 2025.

  • Any new namespace would be decided by the individual specification committers after the move.



--
Thanks
Emily

_______________________________________________
microprofile-wg mailing list
microprofile-wg@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/microprofile-wg


--
Code, TestWrite, Cycle, Run, Drink, Sleep ... Repeat
Java Champion
Lead Java Queue Editor, InfoQ
Contract Developer Advocate, Payara

Laissez Les Bon Temps Rouler


--
Thanks
Emily

_______________________________________________
microprofile-wg mailing list
microprofile-wg@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/microprofile-wg

Back to the top