|
Emily,
We already had this discussion on Jakarta EE Platform meeting and tried to discuss it on one of CN4J meetings with the following conclusion:
1. CN4J meetings are not for technical discussions.
2. We will create Jakarta Config project and invite there all interested parties including MicroProfile Config committers. The first task for this group is to carefully analyse MP Config and decide which parts of it should be moved to Jakarta
which are not. It may be agreed that the whole MP Config should be moved without any changes, it can be agreed that MP Config suits Jakarta EE only partially. I don’t know the answer yet and not
making any assumptions. It’s what Jakarta Config project will decide the open way. Java package and Maven coordinates will also be part of this discussion. As you mentioned, Jakarta Config is in creation review now. I expect it to be created at the
beginning of June. That time the project group will start working. We all will be happy to discuss your and Scott proposal there.
3. When the analysis and discussion is finished, Jakarta Config team will come out with the final plan.
Thanks,
Dmitry
As some of you might be aware,
Jakarta Config Creation Review was created recently by Dimtry (Thanks Dimtry!). The plan is to work with the MicroProfile Config team to define Jakarta Config to be included in Jakarta Core Profile.
The next step is to work out the content of Jakarta Config. From the recent survey done by Reza, it seems majority votes went to move MicroProfile Specs to Jakarta EE (see
here for the survey result blog written by Reza). The top 2 choices are either updating MicroProfile Namespace or keeping the existing MicroProfile namespace.
The community voice is very important to us, but I would also like to gather some consensus from Working group members to agree on the final direction as this impacts both MicroProfile and the Jakarta community. We need to agree on a solution
working for both MicroProfile and Jakarta. With this, I would like to start the discussion of moving MicroProfile Config to Jakarta EE and rebrand to be Jakarta Config 1.0
without updating namespace and then the future development will evolve in Jakarta EE and any new classes and packages can still use org.eclipse.microprofile.*.
Here is the
proposal that Scott and I put together. Let's start this conversation on the mailing list first. If necessary, we can schedule a call to discuss further. Please share your thoughts here.
_______________________________________________
cn4j-alliance mailing list
cn4j-alliance@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cn4j-alliance
|
