Jakarta EE Platform Call

Date: 2024-03-05

Present:

• Arjan Tijms (OmniFish)
• Jan Westerkamp (iJUG)
• Jared Anderson (IBM)
• Ed Burns (Microsoft)
• Emily Jiang (IBM)
• Jim Krueger (IBM)
• Riva Philip (IBM)
• Nathan Rauh (IBM)
• Tom Watson (IBM)
• Jimmy Wu (IBM)
• Vignesh (IBM)
• Nathan Erwin (Individual)
• Ivar Grimstad (Eclipse Foundation)
• Brian Stansberry (Red Hat)
• Scott Stark (Red Hat)
• Dmitry Kornilov (Oracle)
• Petr Aubrecht (Payara)
• Cesar Hernández (Tomitribe)
• Scott Marlow (Red Hat)
• John Clingan (Red Hat)

Agenda and Minutes

Jakarta EE 11 Release Plan

• Wave 1 - 4 release review initiated by 2024-02-29 (leap day) and M2
  • Ivar detailed “what happens next”.
  • Emily suggested sharing the mentor assignment spreadsheet. Select the EE 11 Release Review tab.
  • Spec projects
    • All seem ready to start their release review ballot this week
    • Jakarta Annotations 3.0*
      • https://github.com/jakartaee/specifications/pull/699
      • Staged: https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/annotation/jakarta.annotation-api/3.0.0/
    • Jakarta Expression Language 6.0*
      • https://github.com/jakartaee/specifications/pull/701
      • Staged: https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/el/jakarta.el-api/6.0.0/ \
    • Jakarta Interceptors 2.2*
      • https://github.com/jakartaee/specifications/pull/702
      • Staged: https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/interceptor/jakarta.interceptor-api/2.2.0/ \
    • Jakarta Contexts and Dependency Injection 4.1*
      • https://github.com/jakartaee/specifications/pull/704
      • Staged:
        • https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/enterprise/jakarta.enterprise.lang-model/4.1.0/
        • https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/enterprise/jakarta.enterprise.cdi-api/4.1.0/
        • https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/enterprise/jakarta.enterprise.cdi-el-api/4.1.0/
      • Jakarta Lang Model 4.1
        • (Part of CDI) Scott Stark \
    • Service releases
      • Jakarta JSON Processing*
        • No change. 2.1.3 is out in Maven Central
        • https://repo1.maven.org/maven2/jakarta/json/jakarta.json-api/2.1.3/
      • Jakarta Mail*
        • Lukas
        • Staged: https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/mail/jakarta.mail-api/2.1.3/
        • Is now in maven central this week
      • Jakarta Activation*
        • Lukas
        • Staged: https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/activation/jakarta.activation-api/2.1.3/
        • Is now in maven central this week
      • XML Binding
        • Lukas
        • Staging: https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/xml/bind/jakarta.xml.bind-api/4.0.2/
      • XMS WS (wave 5) * Staging: https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/xml/ws/jakarta.xml.ws-api/4.0.2/
  • 2024-02-29 and M2 actions
    • Ed, Ivar, Arjan
      • Outstanding spec text changes
        • https://github.com/jakartaee/platform/pull/807
        • https://github.com/jakartaee/platform/pull/855
        • https://github.com/jakartaee/platform/pull/854
      • Arjan:
        • Interceptor’s spec should not be in the platform spec, but should be moved into the CDI spec. Functionally, it is CDI-like.
          • Ed, this is a bigger deal. Probably not for 11.
        • Injection of the Principal should be part of the security spec, instead of its current location, the CDI spec. Now moved to the platform spec in PR 855.
          • Jared observed the Servlet aspect, and also points out that the Security spec TCK must test this assertion.
          • https://github.com/jakartaee/platform/issues/841#issuecomment-1962435660
      • Incorporation actions for updated XML Schemas
      • M2 release
        • Keep iterating 11.0.0-SNAPSHOT as artifacts come in after completing their release review then release 11.0.0-M2 from that.
• Update to EE 11 XML Schemas
  • All component spec projects will see their schemas updated to have the version number they are including in EE 11, even if there are no normative changes.
    • Jared observed that we have not consistently done this in the past, for 10, for example. It seems to have been left up to the specs.
    • JEA-341: We the platform project should issue a ruling on this. When the version of the spec is updated, the version of the schemas need to be updated also, to match. Ed to mail to spec-project-leads and platform-dev (and individual emails to spec project leads as well).
      • Scott Marlow did point out that there is a possible time constraint aspect on this. This will take time and people might need to do it for more than one spec.
  • JEA-201
• Wave 5 release review initiated by 2024-03-29
  • Spec projects
    • Jakarta Authorization*
      • Arjan
      • Emily sought a status.
      • Arjan stated the most important part was done a while ago. TCK is part of the platform. RISK FACTOR. Arjan has a plan to mitigate this risk.
        • “Two tck” solution.
        • Policy class removal
        • JEA-345: Ed to capture this into the AzDO for resolution.
      • Emily: will you plan to stage another milestone?
      • Arjan: yes, targeting EE 11 M2 Authorization and Security.
    • Jakarta Persistence*
      • Lukas
      • Riva asked for the status for M2. https://github.com/jakartaee/specifications/pull/703 was filed and review was requested.
      • M2 API in staging since Feb 29
      • Eclipselink 5 was staged a few days ago: https://jakarta.oss.sonatype.org/content/repositories/staging/org/eclipse/persistence/eclipselink/5.0.0-B01/
    • Jakarta RESTful Web Services*
      • Santiago
      • Go for a minimal 4.0
        • Removing JAXB
        • Removing @ManagedBean annotation
        • TCK updates

        • JEA-348: Jim Krueger to submit a PR to

          https://github.com/jakartaee/specifications/blob/master/restful-ws/4.0/_index.md in time for the spec committee to review next week 2024-03-06.

1. Make a fork
2. Clone the fork locally
3. git remote add upstream git@github.com:jakartaee/specifications.git
4. Make a branch
5. Check out the branch
6. Push to your fork
7. Issue a PR from your fork.
   • JEA-349: Ed to submit a PR to https://github.com/jakartaee/platform/blob/gh-pages/jakartaee11/JakartaEE11ReleasePlan.md For all occurrences of “version increment only” change to “service release”
     • Jakarta Server Pages*
       • Mark Thomas and Paul A. Nicolucci
       • M2 API was published to Maven Central last week
     • Jakarta Servlet*
       • Mark Thomas
       • M2 API was published to Maven Central last week
     • Jakarta Validation*
       • Scott Stark
       • Waiting on dependencies to be staged, otherwise ready
     • Jakarta WebSocket*
       • Mark Thomas and Jan Supol
     • Jakarta Tags (previously JSTL) merge into Jakarta Pages (previously JSP)
       • Note: No need for a separate Tags anywhere anymore
       • Busy work with doing service releases, reviews, etc
       • Service release. No need to seek approval from the spec committee.
   • Actions for 2024-03-29 and M3
     • Ed, Ivar, Arjan
       • XML Schemas
       • M3 release
       • Outstanding spec text changes
       • Wave 6
   • Spec projects
     • Jakarta Authentication*
       • Arjan
     • Jakarta Concurrency*
       • Nathan Rauh
       • Released(!): https://repo1.maven.org/maven2/jakarta/enterprise/concurrent/jakarta.enterprise.concurrent-api/3.1.0-M2/
     • Jakarta Faces*
       • Arjan
     • Jakarta Standard Tag Library (dependency update).
       • Paul Nicolucci
   • Actions for 2024-04-27 and M4 release
     • Ed, Ivar, Arjan
       • XML Schemas
       • M4 release
       • Outstanding spec text changes
       • Wave 7
   • Spec projects
     • Jakarta Security*
       • Arjan
     • Jakarta Data*
       • Nathan Rauh
   • Actions: Pardon Ed’s ignorance, but exactly who needs to take actions to make this happen?
     • Ed, Ivar, Arjan
       • XML Schemas
       • M5 release
       • Outstanding spec text changes
       • Wave 8
   • Platform Projects
     • Jakarta Platform* (including appropriate content formerly in CDI EE)
     • Jakarta Web Profile* (including appropriate content formerly in CDI EE)
     • Jakarta Core Profile*
   • Actions:
     • Ed, Ivar, Arjan
       • XML Schemas
       • Final release
       • Outstanding spec text changes

Other business

• Jakarta Data developments
  • JEA-336
  • JEA-340. Ed to update release plan. Change “Wave 6, 7 specs release review initiated by 2024-04-27” to “Wave 6, 7 specs release review initiated by 2024-04-27. Exception for Data. Data will initiate release review by 2024-05-31.”
• Individual specification TCK requirements for specs getting major/minor updates in EE 11
  • JEA-338
  • https://github.com/jakartaee/jakarta.ee/issues/1868
• EJBHome issue, raised by Jared Anderson. Platform TCK has to cover the platform requirements, and no more. For the EE 11 release, EJB will still be included. EJB includes 2.x interfaces. All optional components will be removed unless they are specifically included by the platform. Will the EE 11 platform include the requirement for EJB 2.1 to be implemented or not.
  • If it is not, should we produce an EJB jar that does include them? An optional jar?
  • There’s the TCK side
  • There’s the platform side.