Date: 2026-09-29
Present:
- Cesar Hernandez (Tomitribe)
- Jared Anderson (IBM)
- Kyle Aure (IBM)
- Neena Jacob (IBM)
- Anand N K (IBM)
- James Perkins (IBM)
- Nathan Rauh (IBM)
- Reshmi Vijayan (IBM)
- Jan Westerkamp (iJUG)
Top of mind for Jared, James
- CCRs
- 30 new CCRs from Payara and 1 from Fujitsu
Jakarta EE 11
- Steering committee wants us to finish the retrospective action items
Jakarta EE 12
- M8 week 1 of 6 starts this week (M8 ends November 15)
- Steering committee wants dates to be decided for Web Profile and Platform
- Release plan current states 1Q / Q2 2027. Need more precise dates
- March 31 for Web Profile / May 15 for Platform
- Need to communicate to all component specs to get their buy in
- Core Profile progress
- Targeting 4Q 2026. JakartaOne is December 1
- Core profile spec updates should be started as well to reflect version changes at least.
- Annotations
- No traction for a 3.1 release yet.
- CDI
- 5.0 Final release is published
- Need to fix up some stuff with the TCK publish
- CDI published to the jakarta location when the specification committee should have done that with signature signing.
- JSON-B
- 3.1.0 M1 API and TCK is out
- M2 is in good shape. Just a few updates to be made for some testing and spec for record support
- 3.1.0 M1 Yasson is released. It passes the M1 TCK
- M2 release had issues if you update to latest version of maven
- Requires an update to the parent pom
- Specs will need to update to the new version
- 3.0.3 release to maven is missing directories showing the release
- JSON-P
- No M1 yet, but is planned
- Kyle trying to get committership with some PRs
- REST
- No M1 yet
- Waiting for reviews before anything can be merged
- Committers have been encouraged to review the relevant PRs
- Movement has started to happen
- Arjan expressed interest in https://github.com/jakartaee/rest/issues/1348 being part of the spec for security usage
- Web Profile progress
- Authorization
- No API update yet in Jakarta
- Need Platform vote to move it to Web Profile
- Look to start that vote today
Subject: BALLOT to include Authorization in Web Profile 12
This email indicates the start of a ballot for inclusion of Jakarta Authorization into the Jakarta EE Web Profile 12.
To summarize discussions from the platform calls in the past:
- Jakarta Security and Jakarta Authentication are part of Web Profile, but Jakarta Authorization is in Platform only today
- Jakarta Security does authorization functions, but doesn’t depend on the Authorization modules from Jakarta Authorization to do it
- Authentication and Authorization both weren’t in web profile in the past and authentication was depended on by security and it moved
- Ran out of time for authorization work
Vote +1 (positive), 0 (abstain), or -1 (reject) on this BALLOT to indicate your preference regarding whether or not to include the Authorization specification in the Web Profile. This vote will be counted by simple majority of Platform Project committers as listed in https://projects.eclipse.org/projects/ee4j.jakartaee-platform/who (note that there is no veto). Any feedback that you can provide to support your vote will be appreciated. This will be a fourteen-day ballot, ending on Tuesday, October 13, 2026 or when all committers have voted, whichever comes first.
Non-committers are encouraged to vote as a measure of community sentiment.
- Servlet
- 6.2.0 M2 API was released around May
- The specification page still needs to be updated to reflect this version
- Pages
- 4.1.0 M2 API also release around May
- Tags
- 3.1.0 M2 API released in July
- Faces
- 5.0.0 M6 API released
- Glassfish vNext has faces updates in it
- Security
- 5.0.0 M2 API released in May
- Still need to rehome the API without “enterprise” in the group name
- Glassfish vNext has security updates in it
- Transaction
- Spec / API updates, but no milestone of the API yet.
- TCK move over from platform PR is there for them to accept
- Depends on some TCK shared libraries that would want to have an EE 12 TCK milestone release
- Concurrency
- 3.2.0 M2 API released in March
- Working on API updates for issues found
- Looking to release a M3 soon
- IBM Liberty is working on implementation. It is the usual ratifying implementation
- Data
- 1.1.0 M4 API released
- Appears not to be there fully in maven
- Depends on Query releasing before can do final release
- Expression Language
- 6.1.0 M2 API released in May
- Persistence
- 4.0.0 M7 API released 2 weeks ago
- The specification page still needs to be updated to reflect this version
- Depends on Query releasing before can do final release
- The OmniFish folks are working on EclipseLink 6
- Query
- 1.0.0 M2 of the specification is available
- No API
- TCK covered by Data, NoSQL and Persistence
- Validation
- 4.0.0 M1 API released in October 2025
- WebSocket
- 2.3.0 M2 API released in January
- Enterprise Beans Lite
- Glassfish 9
- Open Forum
- Future directions call last week
- A discussion on MicroProfile/Jakarta EE namespace considerations
- General agreement on the need to move forward.
- Arjan would like to move the MP working group to Jakarta
- Willingness to compromise on some of the issues like namespace
- Jan believes each Working group has some homework that can be worked on.
- TCK package name requirement in Jakarta isn’t how MP does things.
- Discussion on things like moving MP rest client to Jakarta REST not requiring namespace update possibly
- Similar with JWT and Config of course
- MicroProfile update
