Using Micorprofile specifications in Jakarta EE was suggested and discussed many times and the outcome was always that it's not possible. And for multiple valid reasons. One is the problem with cyclic dependencies as Steve suggested. Another problem is that MicroProfile moves faster and sometimes breaks things, which isn't compatible with Jakarta EE goals. Even the Red Hat's view cited by Scott Stark in the beginning of this thread confirms that "Jakarta EE should focus on maintaining stability and backwards compatibility", so I don't understand that Red Hat in the same statement suggests that Jakarta EE should build on top of MicroProfile.
What I think is possible and could be a good compromise, is that a specification is completely moved to Jakarta EE as is, with only minor modifications, which ideally don't break the API. It would mean that such specifications would retain the org.eclipse.microprofile prefix. A lot of people don't like this idea but I think we need to find a compromise to prevent fragmentation and disputes, and such a compromise looks viable to me.
Then we would have 3 kinds of specifications:
* purely MicroProfile specifications, build on top of EE
* purely Jakarta EE specifications, built within Jakarta EE, can be consumed by MicroProfile (e.g. specs in the Core Profile)
* Jakarta EE specifications which originated as MicroProfile specifications, with org.eclipse.microprofle prefix. These would retain as much backwards compatibility with their latest MicroProfile version but adopt the goals of Jakarta EE like stability and backwards compatibility.
In the case of Config, I can imagine that it would be the 3rd case. However we need to consider the impact on Jakarta EE, because config is an essential feature and it might be confusing if the API doesn't use the jakarta prefix.
In the case of JWT, I think it makes a lot of sense to create a light profile for Jakarta Security that doesn't depend on Servlet, integrate JWT into this light profile, and keep the org.eclipse.microprofile prefix for it. The full profile of Jakarta Security could integrate JWT even further where it makes sense.
All the best,Ondro Mihalyi
Director, Jakarta EE expert
Omnifish OÜ, Narva mnt 5, 10117 Tallinn, Estonia | VAT: EE102487932