Jakarta EE Platform Call

Date: 2026-05-12

Present:

• Jared Anderson (IBM)
• Kyle Aure (IBM)
• Anija K A (IBM)
• Chithra Mini (IBM)
• Anand N K (IBM)
• Anagha Paulson (IBM)
• James Perkins (IBM)
• Nathan Rauh (IBM)
• Tom Watson (IBM)
• Michael Redlich (Garden State JUG)
• Ivar Grimstad (Eclipse Foundation)
• Bernd Müller (Ostfalia)
• John Clingan (IBM)
• Scott Marlow (IBM)
• Cesar Hernandez (Tomitribe)

Top of mind for Jared, James

• No new CCRs this week
• James: There is a hard-coded project.build.outputTimestamp in the org.eclipse.ee4j:project parent pom:
  • https://github.com/eclipse-ee4j/ee4j/blob/6c2a2ade8719fc763e021365655e94f60b6a1834/parent/pom.xml#L102
  • Seems to have come in through a PR to make the build reproducible, but that seems wrong to me.
  • Ivar explained that this was done on purpose and discussed in 2020 for reproducibility
  • It is done to workaround a problem in maven where maven adds metadata in the jar
  • There is speculation that something may have been fixed in maven 4 or we can not put the maven metadata in the jar
• Platform TCK 10.0.7 has been released
• Working to release Platform TCK 11.0.3 this week
• Ivar is running the meeting on May 26 since both James and Jared are out

Jakarta EE 12

• M4 week 6.5 of 6.5 starts this week (M4 ends May 15)
  • Core Profile spec statuses
    • REST 5.0
      • Do not expect a M1 to be ready by May 15
    • JSON-B
      • Will not have a M1 release by May 15
      • Kyle is working to become a committer. The vote only had one vote so far
      • The vote ended without enough votes and will be restarted to hopefully get Dmitry and Otavio to vote
      • Need to get the CI pipelines updated with the new parent pom version and get things building to make an M1
    • JSON-P
      • Only changing API to remove SecurityManager usage and updating javadoc. Doing service release for Parsson if needed, but may not be needed
      • Need to get the CI pipelines updated with the new parent pom version and get things building to make an M1
      • Will not have a M1 release by May 15
    • CDI
      • Still on Alpha6. As reported last week, a couple of updates needed still and should be close to being done.
    • Annotations
      • No changes done so far.
      • Previous discussions were around adding a virtual thread annotation for issue 1037
      • If we do not plan to do this for EE 12, we could move that issue to EE 13
      • Instead of an application adding an annotation for virtual thread, it may make sense to have a configuration / annotation to have the platform implementation use to decide if work with that configuration can be run on virtual threads.
      • Presently Jakarta Annotations doesn’t have a lot of active committers
      • We may want to pull it under the control of the platform project, still as a standalone spec, but managed by the platform since it is so platform scoped. Similar to how ManagedBeans was done in the past
      • Would need to have a project restructuring discussion
      • First need to see if we want to have EE 12 have an update for Annotations and see if we can add committers
      • ACTION: Need to work with annotations spec community to get additional people added to make updates if we want to have something in EE 12. Dmitry is the lead for Annotations
    • Jakarta Config
      • Needed for some other specs like NoSQL and if we want to do new things with Resources / DataSources, remove JNDI for instance
      • This is all tied up still with the MP Config discussions
  • Still need to update GH board and platform release schedule
  • https://jakarta.ee/release/12/ now exists
    • If NoSQL comes in for EE 12, would expect it to be in the Web Profile and not just the Platform
  • Tanja’s previous email about cleaning up project committer list to remove old committers who are not part of the community any longer is here.
• Conference updates from Ivar
  • Ivar has been at ShiftAPPens hackathon with 150-200 students (high school and college). Many never used Java or Jakarta and really like to use it. Used different implementations that they picked.
  • Also visited University of York and presented Jakarta EE there
  • Also JavaConnect KE in Nairobi talking about AI and Jakarta. SpringBoot and Quarkus were being used there.
  • Dev Advocate activities link
  • To help new developers, may be good to help get them bootstrapped to guide them
  • Or maybe a maven plugin like doing maven jakarta run that hooks into implementations’ existing implementation to improve the developer experience
  • An expansion of the existing Jakarta EE Start project: https://start.jakarta.ee/ possibly
  • Cargo Tracker example application can be helpful to give people examples on how to use the Jakarta platform