80 MB, 1000 files, 7 releases limits per month allowed unless you do a paid service or get an exemption
Jakarta EE 12
M5 week 6 of 6 starts this week (M5 ends June 30)
Security 5.0 and Faces 5.0 working on a new milestone
Core Profile progress
CDI
Beta1
JSON-B
3.1.0 M1 is now out
Kyle is out for 6 weeks
JSON-P
No M1 yet, but is planned
REST
Neena from IBM is helping getting some issues worked on
Moving forward without arbitrary CDI method injection. Easier for everyone
Jersey tracking changes for REST
Jan Supol not at Oracle any longer
May need to change project lead possibly
REST process is 3 committers to approve and two weeks
NoSQL update (if Otavio comes)
Persistence
EclipseLink also hit hard by Oracle resource reduction
Will need people to be involved in EclipseLink in order to improve coverage of spec
If there is no new version for 4.0 for EclipseLink, it will make it hard on the customers who rely on EclipseLink
It may be a failure of the spec that it is hard to migrate between implementations of the spec. It is better than migrating if using the native API of the implementations of course
Vendor app servers who rely on EclipseLink need to push it forward – Glassfish, OmniFish, Payara, Fujitsu, others
MP
Topic added to the steering committee meeting
Maybe move Config Core part first
Config Core and Config CDI could evolve independently and have different version numbers even in the future
There is also an issue with Java package names for TCK to be the same as the API which isn’t allowed in Jakarta, but is done in MP. Getting an exception would help for MP moving to Jakarta
From Maven perspective, there are multiple variants of how Jakarta projects are set up. Some use a parent with api, spec and tck, but others do not have parent and could have multiple repositories that makes it difficult as well
Jakarta EE 11
Working to get Core Profile, JSON-P, Faces TCK updates for Jakarta EE 11 to be able to run on Java 25. Mostly date format changes due to new standard versions. JSON-B already done
