Jakarta EE Platform Call

Date: 2022-01-04

Present:

• BJ Hargrave (IBM)
• Jan Westerkamp (iJUG)
• Thomas Watson (IBM)
• Ed Bratt (Oracle)
• Ivar Grimstad (Eclipse Foundation)
• Emily Jiang (IBM)
• Nathan Erwin (Individual)
• Lukas Jungmann (Oracle)
• Roberto Cortez (Red Hat)
• John Clingan (Red Hat)
• Petr Aubrecht (Payara)
• Majid Mostafavi

Agenda and Minutes

Jakarta EE 10 Status (standing agenda item)

• Hard deadline of Feb 28 2022 for component specifications to release an update for EE10

• Ballots: https://www.eclipse.org/lists/jakarta.ee-spec/2022/Jan/index.html

• List of projects that can be “blockers” if they don’t release
  • Dependency Graph (Ivar will put link here)
• Specs without draft PRs created
  • Jakarta Messaging 3.1
  • Jakarta Concurrency 3.0
  • Jakarta Persistence 3.1
  • Jakarta SOAP with Attachments 3.0
  • Jakarta WebSocket 2.1
  • Jakarta JSON Binding 3.0
  • Jakarta Authentication 3.0
  • Jakarta Authorization 2.1
  • Jakarta XML Binding 4.0
  • Jakarta XML Web Services 4.0
  • Jakarta Connectors 2.1
• Lots of these depend on Activation

[Emily] Package naming convention for TCKs?

• Packages for TCK starts with various names, e.g. org.ibm, org.jboss, org.eclipse, jakarta.[spec].tck etc

• Should they be standardized?

• Concensus about the following:
  • Two things need naming standard:
    • Packages
      • Suggested Naming Standard: **jakarta.tck.[spec] **
      • New classes in existing TCKs should use the new name standard
    • Artifacts
      • Same group id as the spec
      • Artifact ids [foo]-tck
  • Existing TCKs may change if they like
  • New TCKs must use the new name standard \
• Emily will send the suggestion it to the mailing list(s) to get input

[Jan] Dependency graph tooling

• During the iJUG Cyberland Code Camp an experiment with JQAssistant analysing Jakarta EE 9 dependencies including a generated one for Java SE (with Dirk Mahler and Gerd Aschemann). Further analysis is planned.