|Re: [jakartaee-platform-dev] Release profiles independently|
More than one maybe two additional profiles were not suggested e.g. by Scott Stark’s document or the call today.
As for MicroProfile, Config may Benefit because it has fewer upstream depencencies than most of the other MP stuff. And except RestClient (ideally folded into REST because that is really a Logical candidate for that) the majority of others are „glue“ and not real specifications of their own, so they would not make much sense in some Kind of profile outside MP itself.
Look at Spring Framework vs. Spring Boot, most of the core funcationality like config properties existed long before Spring Boot and there’s a reason the other functionality like Health Actuators etc. did not become part of the Spring Framework itself either.
I did not suggest Jakarta EE 10 without new features.
What I suggested is to release new specs under Jakarta EE 10, but select which ones should go first under "New profile" and release that profile ASAP.
Then release other profiles. Of course it does not exclude the possibility to release all profiles at the same time.
For me the list of specs that should be improved and released first is (sorry for old names):
CDI (As an alternative to EJB)
Goodies from Microprofile like Config, RestClient, OpenAPI, Health, Fault Tolerance
On Tue, Mar 16, 2021, 8:33 PM Werner Keil <werner.keil@xxxxxxx> wrote:
Back to the top