| Re: [jakarta.ee-spec.committee] Werner's comment |
It certainly is relevant to the enterprise java space, and it has no dependencies on any other MP spec.They were intending to use the javax namespace, so it would be jakarata now.On Thu, Aug 30, 2018 at 8:28 AM Richard Monson-Haefel <rmonson@xxxxxxxxxxxxx> 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?On Thu, Aug 30, 2018 at 10:15 AM, Mike Milinkovich <mike.milinkovich@eclipse-foundation.org > 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.
_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakarta.ee- spec.committee