Skip to main content

Jakarta EE Platform Project

Home for the Jakarta EE Platform Team

Jakarta EE Platform Call

Date: 2025-01-07
Present:

  • James Perkins (Red Hat)
  • Jan Westerkamp (iJUG)
  • Ivar Grimsad (Eclipse Foundation)
  • Ed Burns (Microsoft)
  • Jared Anderson (IBM)
  • Anand NK (IBM)
  • Nathan Rauh (IBM)
  • Tom Watson (IBM)
  • Gurunandan Rao (Oracle)
  • Tanja Obradovic (Eclipse Foundation)
  • Dmitry Kornilov (Oracle)
  • Ed Bratt (Oracle)
  • Brian Stansberry (Red Hat)
  • Bernd Müller (Ostfalia)
  • Petr Aubrecht (Payara)
  • Cesar Hernandez (Tomitribe)
  • Scott Marlow (Red Hat)
  • Kenji Kazumura (Fujitsu)

Agenda

Top of mind for Ed, Arjan, Jared

  • Ed has requested help from Will Lyons from the Steering Committee to have an intervention to get the new Jakarta EE 11 TCK completed so we can be done with EE 11. Will has agreed and is planning to attend the TCK call tomorrow.
    • There is a chance that some of our previously discarded “hybrid 10+11” type options may be put back under consideration. I strongly don’t want to be dealing with this in EE 12, so I ask Scott Marlow to give some thought to why those options are undesirable.
  • Ed hasn’t completed his assigned action items regarding releasing the core profile maven artifacts for the TCK in a compliant way with the specification committee guidance. This task is still assigned to Ed.
    • [Ivar] The Core API artifacts were released right after the ballot concluded successfully according to the process.
      https://central.sonatype.com/artifact/jakarta.platform/jakarta.jakartaee-core-api
    • [Ivar] The Spec page has not been updated (PR has not been merged yet).
      • The reason the PR has not been merged is that the TCK release has not complied with the new requirement.
      • The decision to not comply with the new requirement is within the authority of the platform project.
        • The platform project proposes we publish the TCK zip as is and follow a manual process to extract the TCK maven artifacts and publish them to maven central. See comment on PR.

TCK Refactoring Jakarta EE 11

  • Arjan provided an update. In his telling, the TCK structure is still in a bit of disarray. More organization is necessary.
    • Code that is not on the critical path for releasing EE 11 is still present in the TCK. This code should be moved to component TCK tests. For example, some Tags tests.

  • Discussion about test placement from Jan:

    I think for the allocation of tests in the Component or Platform TCK should follow their test dependency requirements - if they need to add dependencies beyond their Spec and API dependencies, then they need to be placed separately in the component spec as a minimum or must be part of the Platform TCK.
    The Component Spec TCK should support different environments like Java SE, Core Profile, Web profile and Platform - or even something like Servlet Container (only).

    Some of these dependency issues might be solved by moving the test from a lower wave component spec TCK to a higher wave component spec TCK instead of putting it into the Platform TCK.

Jakarta EE 11

  • Authentication 3.1.1 TCK update
  • Servlet 6.1.1 TCK update
  • Validation 3.1 API
    • Validation implementation cannot go final until some files are added / updated in the API jar.
    • When will we get a new 3.1.1 release of the API?

Jakarta EE 12

Back to the top