Re: [microprofile-wg] [STRAW POLL] MicroProfile->Jakarta Namespace, vote

[Roberto Cortez <radcortez@xxxxxxxxx>]

+1 (Red Hat) on keeping the namespace:

- A namespace is mostly a technical detail (these days mostly hidden by modern IDE’s). While there was a very good reason for the javax -> jakarta move (with all the pain that brought), a simple “alignment” justification is not enough to go through that pain again (to a lesser extent)

- MP Config may be deprecated in a new Jakarta Config spec, MP REST Client may merge with Jakarta REST, JWT may merge with Jakarta Security. There is no added benefit in rushing any namespace change without discussing what is going to happen with each MP API (if they are going to continue standalone or merged into another Jakarta spec). In the event of a merge between two APIs, we agree on a namespace change. Standalone specifications should stay as is.

- We do support a release in the Jakarta GAV with relocation to the MP GAV. This should alleviate some of the initial concerns regarding consistency and alignment.

Cheers,

Roberto

On 12 May 2025, at 20:32, John Clingan via microprofile-wg <microprofile-wg@xxxxxxxxxxx> wrote:

This is a non-binding straw poll vote-only thread. The discussion thread is here.  Please consider this a “red line” vote, meaning a “-1” vote would also mean a -1 vote on MicroProfile joining Jakarta EE. Please vote by May 19th, 2025.

"If MicroProfile is to join Jakarta EE, keep the org.eclipse.microprofile namespace for existing specifications.” 

_______________________________________________
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