Jakarta EE Platform Call

Date: 2023-10-31

Present (please put your name down here to mark yourself as present…):

Agenda and Minutes

Created GitHub milestone to track those that have already been published to maven central
- https://github.com/jakartaee/platform/milestone/2
Annotations done.
- Thanks.
Data update
- M1 API and TCK in maven
- Nathan enumerated the steps he has been taking to minimize late-breaking objections from stakeholders with different opinions of design.
- Shared positive stories of engagement from these diverse stakeholders.
Others that have a maven artifact
- cdi, cdi-el, lang-model have Alpha1 for API and up to Alpha5 for TCK
- interceptor has RC1
- persistence has B01

I’d like to get clarity on whether or not we attempt this in EE 11. My gut instinct right now is: no. maybe.
The group discussed several aspects.
- The “override” case (if the vendor does not like the defaults)
  - Platform defines the WebProfile interface, as in this proposal.
  - This interface has a “lineup” of all the versions of all the specs in that platform.
  - What about if an impl of a component spec wants to override?
  - Do we need to consider this corner case?
  - If so, isn’t this a kind of “config”, and if so, shouldn’t we be looking at this as Jakarta Config?
  - What about the good old fashioned “Service Loader” technique?
    - CDI and JSON specs currently use this.
- Dmitry gave an update on Config: Not available for use in EE11.
Ed polled the group on the utility of the idea in general.
- Arjan and Nathan shared concrete examples for doing this.
We would need to add TCK
- Platform TCK
- Web Profile TCK
- Core Profile TCK

Scott Stark had already agreed to do this.
- Ed to check with Scott and confirm that he still accepts this heavy mantle.
One of the existing committers just has to propose Scott Stark.