Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [] Fork Eclipse MicroProfile Configuration as Jakarta Configuration.

If Jakarta Config went through the JESP then the IP would be clean enough. It is not necessary on the Jakarta side to wait for the MP WG to sort itself out.

MP specs aren't going to be consumable in their raw state due to the pull model approved by MP and the desire to support both MP and Jakarta in a single runtime. Bidirectional dependencies between the initiatives with different cadences and stability goals will be a nightmare. This concern was raised on the MP side but dismissed as "not our problem".

Also any MP spec may need changes to cleanly integrate to ensure a consistent experience in the Jakarta EE platform and the Jakarta platform has different stability requirements. The MP statement is to forge ahead without regard to consumers of specs.


From: <> on behalf of David Blevins <dblevins@xxxxxxxxxxxxx>
Sent: 02 April 2020 2:24 AM
To: Jakarta EE community discussions <>
Subject: Re: [] Fork Eclipse MicroProfile Configuration as Jakarta Configuration.
On Apr 1, 2020, at 8:33 AM, Kevin Sutter <sutter@xxxxxxxxxx> wrote:

Yes, there is another option...  Wait a month or so while MicroProfile figures out a Working Group proposal.  The MP community and the EF are both in favor of establishing a separate MP Working Group as a first step.  Once this is established, then the Specifications (and APIs and TCKs) will all be properly covered from an IP standpoint and they could be consumable by Jakarta EE projects.

Right.  And specifically we don't just need the Working Group in place with a specification process, but we need to actually do a release of MicroProfile Config under that process.

We're a few months away from having IP clean enough for any proposal on the Jakarta side to move forward.

In short, our current status: eat your meat so you can have your pudding. :)


Back to the top