Skip to main content

Jakarta EE Platform Call

Date: 2026-03-03

Present:

  • Jared Anderson (IBM)
  • Kyle Aure (IBM)
  • John Clingan (IBM)
  • Neena Jacob (IBM)
  • Anija K A (IBM)
  • James Perkins (IBM)
  • Nathan Rauh (IBM)
  • Reshmi Vijayan (IBM)
  • Tom Watson (IBM)
  • Nathan Erwin (Individual)
  • Scott Marlow (IBM)
  • Cesar Hernandez (Tomitribe)

Top of mind for Jared, James

  • No new CCRs this week
  • Platform TCK meeting this week at 11:00 ET on Wednesday
  • Meetings will be off schedule starting next week due to DST switch in the US and Canada on March 8 at 2:00 AM
    • 3 weeks will be 1 hour earlier in non US / Canada locations until the March 31 meeting
    • ACTION: Send an email to the platform mailing list
  • OSSRH
    • 2.0.1 version of the parent POM is created

Jakarta EE 12

  • Week 3 (of 6) for M3 for the platform (ends March 31)
    • Component updates
      • Rest - James is working on the CDI integration work
      • Data - Not working on a M3 yet, but can do that soon if there are changes
      • Concurrency - Working on M2
        • Working on a rename of the maven namespace from jakarta.enterprise.concurrent to jakarta.concurrency
        • There was a push to remove enterprise from the group ids
        • Where was the push from? July 2024 platform call maybe. Will look it up.
        • CDI has already made the transition
        • Security has jakarta.security.enterprise and it sounds like they are also making a transition as well to jakarta.security
    • Transaction read-only change that affects other specs
      • Nathan identified that what was proposed was unsafe and provided an alternative proposal that will be safer
      • Until this is resolved, other specifications (for example connectors) are holding off on making updates to their spec language to handle read only transactions
  • MP updates
    • MP technical call was last week
    • MP 7.2 targeting July 21, 2026
      • Quarkus is the planned ratifying / first compatible implementation
      • Will support EE 10 and tolerate EE 11 like 7.0 and 7.1
  • Yasson has lack of committership
    • Kyle has been working to get committership by reviewing changes and making changes, but nothing is getting merged due to no committer seeming to be active
    • Kyle and James submitted to be a committer, but that was stopped because no one voted because it appears to not have any committers to vote
    • May need to start a conversation with EMO to get things moving
    • Tanja also started this conversation in the mailing list about active vs inactive membership in communities and needing to move people to the historic committers list where appropriate
  • Eclipselink also is in a similar state
    • Listed leaders seem to be inactive at this point due to organizational changes at different companies
    • There are at least 2 active people on the committer list (Arjan and Anija) that were recently added, but I don’t think they will be able to lead the community
    • Working to release a new service release of the persistence TCK and want to validate the service release against EclipseLink to show that the service release doesn’t fail

Back to the top