Skip to main content

Jakarta EE Platform Call

Date: 2021-04-27


  • Kevin Sutter (IBM)
  • Scott Marlow (Red Hat)
  • Ivar Grimstad (Eclipse Foundation)
  • Jean-Louis Monteiro (Tomitribe)
  • Otavio Santana
  • Lukas Jungmann (Oracle)
  • Thomas Watson (IBM)
  • Ed Bratt (Oracle)
  • BJ Hargrave (IBM)
  • Brian Stansberry (Red Hat)
  • Dmitry Kornilov (Oracle)
  • Scott Stark (Red Hat)
  • Steve Millidge (Payara)
  • Ryan Cuprak (Jakarta EE Ambassadors)
  • Kenji Kazumura (Fujitsu)
  • Jesse McConnell(Webtide)
  • Emily Jiang (IBM)
  • John Clingan (Red Hat)

Agenda and Minutes

Jakarta EE 9.1

  • Platform 9.1 PR ( - merged
  • Specifications 9.1 PR (
    • Will be updated up until Friday
  • Merging service release versions to API JAR
  • CCRs
    • GlassFish - ok
    • OpenLiberty - on the way
    • WildFly Preview - on the way
    • TomEE - working on wrapping up the last tests for Jakarta REST
    • Payara - planning to release an alpha around the release date

Jakarta EE 8.0.x service release request (volunteers?)

  • (related)
  • (related)
  • Produce new BOM
  • TCK run? Should not be required if changes are limited to BOM generation
    • Probably requires a separate issue for creating TCKs for validating BOMs in a future release (post 9.1)
  • Create PR to specifications repo for approving
  • Regarding how long to handle Jakarta EE 8.x TCK challenges, we will continue to handle them.
  • Will bring this up next call. Anyone interested in pushing this service release through can contact the platform team. A great way to learn the release process!

Jakarta EE Core Profile

  • Update scope statement “To provide a profile that contains a set of Jakarta EE Specifications targeting smaller runtimes suitable for microservices as well as allowing compilation to native images.”
  • Core Profile implicitly requires CDI Lite

Jakarta Config


Suggested Discussion Topics

  • Release- and versioning strategy
  • Java SE versions
  • JPMS Strategy
  • Standalone TCK Guidance
  • Architectural Guidelines Document
  • Handling of specification TCK tests that reference other specification containers Need to define how specification TCKs that reference other specification containers are handled

Back to the top