This is a great direction and it is an easy +1 from Microsoft.
In terms of naming, things like Jakarta Health is a lot less of a
mouthful than Jakarta MicroProfile Health. We do believe
maintaining the MicroProfile brand and differentiation is
important and valuable. For example, the resulting new Jakarta
Profile could be called "Micro Profile". Similarly, associated
sensible package names that would be clear to the community and
customers could be: jakarta.microprofile.*. Unfortunately things
like org.microprofile.* inside Jakarta EE may prove to be too
confusing as it implies a separate domain.
Using any other namespace instead of org.eclipse.microprofile.* would cause unnecessary migration effort. People might still remember how hard the Eclipse Foundation tried to keep the javax namespace to avoid the migration effort. Right now, we have the pleasure to keep the microprofile namespace. Why should we throw away the luxury and force the MicroProfile customers to go through migration? As for the spec name, it is less important as it has not much application impact.
Thanks
Emily
From a Microsoft standpoint, we will do whatever we sensibly can
to ensure this is not seen as a zero sum outcome dynamic for
anyone and only a net gain for all.
On 3/19/2025 4:37 PM, John Clingan via
microprofile-wg wrote:
At
yesterday's MicroProfile Steering Committee call, John and Emily
presented "Proposal: Host MicroProfile in Jakarta
EE".
Before replying to this post, please review the meeting minutes to
see what has been discussed. Please use this thread to continue
the discussion. The proposal is at a high level, and some
details would need to be worked out if this proposal moves
forward.
However,
for the proposal to move forward, we would need to have a vote.
We are not there yet because the details matter.
Let's
discuss the details in this thread, which is dual-posted to the
Google Group and the MicroProfile Working Group email alias.
For
those that attended the meeting, please review the minutes for
accuracy.