Re: [jakarta.ee-spec.committee] Werner's comment

[Mike Milinkovich <mike.milinkovich@xxxxxxxxxxxxxxxxxxxxxx>]

On 2018-08-30 11:28 AM, Richard Monson-Haefel wrote:

I see.  Well, if its already a spec in MP and they simply want it recognized as also being a part of the Jakarta EE platform, than that would require that it be germane to the Jakarta EE project.  Is the Config germane, without the context of all the other MP profiles, to the Jakarta EE platform?  Also, I'm assuming that it would maintain its current packaging which is "org.eclipse.microprofile.config " and not use the jakarta package name, correct?

No. In my mind if it is a Jakarta EE specification, it *must* use the jakarta namespace for the specification. Clearly when it was at the JCP the understanding was that it would move its namespace to javax.

But all of this is academic until we hear directly from the project that this is what they actually want.

On Thu, Aug 30, 2018 at 10:15 AM, Mike Milinkovich <mike.milinkovich@xxxxxxxxxxxxxxxxxxxxxx> wrote:

On 2018-08-30 11:12 AM, Richard Monson-Haefel wrote:

Having additional candidates for the process is great. Is this specific to MicroProfile?  If so, than I think it should remain in the MP project. They have their own process for specifications. If its not MP specific and can complement the Jakarta EE platform than I would support adding it as a candidate.

Config is already in MicroProfile. If I am reading this correctly the suggestion would be to make it the first MP spec that moves to the Jakarta EE process. FWIW, there could be good reasons to do so because I expect that there will be Oracle-imposed restrictions on all specs that use the javax namespace, not just the ones where Oracle was the JCP Spec Lead.

On Wed, Aug 29, 2018 at 4:31 PM, Mike Milinkovich <mike.milinkovich@eclipse-foundation.org> wrote:

All,

Werner added a comment to the draft minutes of our meeting today. I cannot keep it as part of the minutes since we did not discuss it on the call, but I thought it was pertinent so wanted to capture it for everyone via this email:

Create a plan to deliver a draft Specification Process for CodeOne/EclipseCon

Creating a draft from scratch may not work there, but in the EG discussion Emily sounded very interested to also migrate the non-final Config JSR to Jakarta EE, see: https://dev.eclipse.org/mhonarc/lists/configjsr-experts/msg00059.html If what was discussed for JNoSQL applies to a future version of the Config Spec, then it would end up with at least 2 package name spaces. Migrating it now before it even entered MavenCentral could avoid that.

---

This email has been checked for viruses by Avast antivirus software. www.avast.com