Skip to main content

Jakarta EE Platform Call

Date: 2023-03-28

Present:

  • Jared Anderson (IBM)
  • Emily Jiang (IBM)
  • Jim Krueger (IBM)
  • Nathan Rauh (IBM)
  • Tom Watson (IBM)
  • Jan Westerkamp (iJUG)
  • Petr Aubrecht (Payara)
  • Arjan Tijms (OmniFish)
  • Werner Keil (Invididual)
  • Ed Burns (Microsoft)
  • Ivar Grimstad (Eclipse Foundation)
  • Dmitry Kornilov (Oracle)
  • Lukas Jungmann (Oracle)
  • Kenji Kazumura (Fujitsu)
  • Cesar Hernandez (Tomitribe)
  • Scott Stark (Red Hat)
  • Jean-Louis Monteiro (Tomitribe)

Agenda and Minutes

  • Start creating EE11 issues
    • Based on input from (but not limited to) Jakarta EE 11 Discussion
      • Decided to close the document and start creating issues based on it
    • Epic suggested for improving the JavaDocs
    • Standardize AsciiDoctor Diagrams for images/diagrams in the spec documents
    • Epic for eliminating TCK technical debt and establishing standalone TCKs
  • Ivar will send out reminder to project leads (action from last week) for plans

  • TCK refactoring is an important epic for Jakarta EE 11
    • Upcoming TCK meeting (April 5) are aiming to come up with a roadmap
      • The roadmap will feed into the release plan for EE 11
    • Servlet TCK may be used as an example for a standalone TCK
    • JSON-B/JSON-P
    • Discussion around JUnit/TestNG/Arquillian
    • Requirements and recommendations from the TCK refactoring will be input to the component spec release plans
  • Ed Burns as release manager update: meeting scheduled to discuss this with management on 2023-03-30.

[Emily] CI job instructions

  • Naming conventions and instructions
    • Emily will create an issue for EE11
  • Which jobs to run before publishing the TCK releases?
  • CI job names (https://ci.eclipse.org/)
  • E.g. Prefix with Jakarta or suffix with
    • Group jobs by owning working group in the UI (?)
  • Issue for naming (CI job created by Emily)
  • For Security project naming issue from “es” to something else:

[Emily] Jakarta Security and MP JWT interlock call

Back to the top