Skip to main content

Jakarta EE Platform Call

Date: 2021-07-20


  • Kevin Sutter (IBM)
  • Jan Westerkamp (iJUG)
  • Tomas Langer (Oracle)
  • Dmitry Kornilov (Oracle)
  • Thomas Watson (IBM)
  • Ivar Grimstad (Eclipse Foundation)
  • Roberto Cortez (Red Hat)
  • Jean Louis Monteiro (Tomitribe)
  • Jesse McConnell (Webtide)
  • Lukas Jungmann (Oracle)
  • Nathan Erwin (Individual)
  • Scott Marlow (Red Hat)
  • Brian Stansberry (Red Hat)
  • John Clingan (Red Hat)
  • Vano Beridze (Individual)
  • Ed Bratt (Oracle)
  • Ryan Cuprak (Jakarta EE Ambassadors)
  • Werner Keil (Individual, Ambassadors)
  • Cesar Hernandez (Tomitribe)

Agenda and Minutes

Release Cadence (continue from last week)

  • Roadmap
  • Time-based vs Feature-based
  • Discussion
    • Does this really have to be decided now?
    • Depends on features being proposed
    • Should we rather focus on a roadmap for future release(s)?
    • What is “the spirit”?
      • Corporate like time-boxed?
      • Or, more open-source minded “Let’s release when we have something”?
      • Jakarta EE WG is a mix of the two
    • Decision: Park this discussion for now. Take it up later if it doesn’t fall out by itself. Focus on the roadmap.

Roadmap planning

  • Goal: Predictability regarding aligning with Java SE releases

  • Jakarta EE 10
    • Java SE 11
    • Component Specs starting releases in Oct, done in Dec? End of 2021
    • Platform/Web Profile in Q1 2022?
    • Core Profile ?
    • TCK ?
    • Which vendors will be able to support/implement EE 10, and in what time frame?
      • Get feedback from implementors (of platform/profiles)
    • What are the compelling features to motivate customers to adopt other than the Java SE version?
      • Config? - should not be a gating factor
      • Other specs will be able to rely on config from next version
  • Jakarta EE 11
    • Java SE 17
    • When? 1 year? 18 months? 3 year?
    • Component specs embracing Java SE 17 features are targeting Jakarta EE 11 - communicate this to the project teams Plan reviews by:
  • Jakarta EE 12
    • Java SE (next LTS after 17)
    • When? 1 year? 18 months? 3 year?
  • Feature based planning, where Java SE level is one of the (key?) features
  • Encourage component specs to come up with releases (and plans for releases)

[Kevin/Ivar] Jakarta EE 10 Release Plan

  • Kevin will send out a draft to the platform team and spec project leads later this week
  • Contains topics we have discussed
  • Feedback wanted from platform team and component specs
  • Add comments and suggestions to the plan for core profile and tck
  • Contains Platform and Web Profile
  • Core Profile can be included later
    • Depends on Config and CDI Lite
    • Should the profile possibly be released without Config?
    • Could be introduced as a new profile without any new significant features/specs
    • Add new specs for a later version of core profile

TCK Refactoring

  • Intention is to use new technologies (maven, Junit5, Arquillian,..)
  • No intention to duplicate tests
  • Tests maintained by a component spec team is pulled in to be run by the CTS for the Platform/Profiles
  • Platform TCK should/will be restructured (multi-module), so there is flexibility as to where the tests are being maintained

Back to the top