Skip to main content

Jakarta EE Platform Project

Home for the Jakarta EE Platform Team

Jakarta EE Platform Call

Date: 2026-02-10

Present:

  • Jared Anderson (IBM)
  • Kyle Aure (IBM)
  • Anija K A (IBM)
  • James Perkins (IBM)
  • Nathan Rauh (IBM)
  • Brian Stansberry (IBM)
  • Reshmi Vijayan (IBM)
  • Tom Watson (IBM)
  • Jan Westerkamp (iJUG)
  • Arjan Tijms (OmniFaces)
  • Michael Redlich (Garden State JUG)
  • Bernd Müller (Ostflaia)
  • John Clingan (IBM)

Top of mind for Jared, James

Jakarta EE 12

  • Thoughts of schedule and milestone dates going forward
    • M3 Feb 15 to Mar 31
    • M4 Apr 1 to May 15
    • M5 May 16 to Jun 30 – possibly Core profile here
    • M6 Jul 1 to Aug 15
    • M7 Aug 15 to Sep 30 – ideally we release here or soon after
    • M8 Oct 1 to Nov 15
    • WE DO NOT WANT TO GO INTO 2027 – Steering committee backed
  • Compatible implementation is the main issue here of course still
    • Vendors still working on their EE 11 releases
    • Glassfish was the ratifying implementation for EE 11. Took 6 months since then to get a final release though that just completed recently
    • Component spec implementations that historically had mostly Oracle committers and many of them are no longer with Oracle.
      • Glassfish depends on these implementations for their implementation
      • EclipseLink is an important one with all the updates in Persistence 4.0 and Data 1.1’s dependency on persistence
      • Parsson and Yasson also are concerning
      • Glassfish has a small team as well
    • M2 date is not listed above. Can consider it for Feb 14 at this point. 🙂
      • Platform doesn’t have a M1 or M2 release. Component specs have release some M1 and M2’s
      • There is some concern about which of the component specs will make it into the platform due to the concerns raised above
    • Standalone vs in container TCK testing
      • Persistence has two copies of the TCK – standalone and in container
      • JSON-B and JSON-P TCK only have standalone tests currently and doesn’t run in the container
      • Data has two run modes – standalone and in container
      • Could arquillian have a JavaSE mode?
    • Some component spec TCKs are still in platform TCK repo
      • Ideally they would move to their component spec repository to make easy to maintain
      • Persistence resists this move due to the in container testing, but that wouldn’t need to be run for compatibility testing of the component spec alone
      • Having spec, api and tck in the same repo makes it easy to put them all in at the same time for an update to the API / spec
    • Specs running independent of CDI in standalone TCK vs relying on CDI innately in the specification and then having the tests with CDI
      • Specs need to have their list of dependencies and have their TCK testing include those dependencies as part of their tests, but doesn’t need the entire profile / platform to test
    • Would need to have component specs ratified by August for including in a platform compatible implementation for EE 12. EclipseLink for example
      • Concern about TCK for persistence for instance since it appears that there are not tests added to the TCK yet
    • Many vendors use EclipseLink, but there are limited committers from those vendors in the EclipseLink community
      • Project leaders for EclipseLink appear to be mostly not around any more / inactive except Dmitry. Some should move to Historical committers probably
      • Project team needs to adjust their leader and committer lists
  • MP update
    • MP 7.2 is pushing for Q3 2026 release at the earliest
    • MP Technical call is today
    • MicroProfile (Config) Future Directions call within Jakarta Future Directions on 5th of February – recording. Accessing recording has permissions issues.
    • Namespace debate == org.eclipse.microprofile.* vs jakarta.*

Back to the top