-
M6 week 6 of 6.5 starts this week (M6 ends Aug 15 (next Saturday))
- Core Profile progress
- CDI
- JSON-B
- 3.1.0 M1 is now out
- Specifications page was not updated to include 3.1-M1. Kyle will take care of that
- M2 is in good shape. Just a few updates to be made for some testing.
- Yasson had to rename its group id to org.eclipse.yasson
- Relocation pom was published to help people find the project from older dependency mappings
- JSON-P
- No M1 yet, but is planned
- REST
- No M1 yet
- Waiting for reviews before anything can be merged
- At this point the steering committee believes we are not going to make M7 (Sept 30) for Core Profile and we are moving to 4Q
-
Agentic AI 1.0-M1 is working on being released: https://github.com/jakartaee/specifications/pull/916
-
Concurrency appears to have a 3.2-M2 API in maven central, but the jakarta.ee/specifications pages still talks about 3.2-M1. No release done for 3.2-M2? Kyle will update that as well.
- Open forum
- Jan talked to Tanja about hearing from others about the Config coming to Jakarta and wanting to know when that will happen
- Jakarta homework for MP coming to Jakarta
- MP is wanting more openness from Jakarta. Meeting recording. Steering and Specification committee guest invites.
- MP wanting an exception for the tck namespace required to be different from the API namespace or remove the rule
- API and TCK both in org.eclipse.microprofile.<spec> group id
- Then there is the API package name we all know with moving from org.eclipse.microprofile to jakarta discussions had ad nauseum
- Customers for Oracle expressed they hated the transition from javax to jakarta. Open Rewrite was not helpful for them.
- Using the MP config API is the simple solution for the customer. Jakarta config adds choice and complication
- Having both could be a moment in time thing to make it easy for migration
