Jakarta EE Platform Call

Date: 2024-02-27

Present:

• Ed Burns (Microsoft)
• Jared Anderson (IBM)
• Riva Philip (IBM)
• Nathan Rauh (IBM)
• Tom Watson (IBM)
• Jimmy Wu (IBM)
• Jim Krueger (IBM)
• Arjan Tijms (OmniFish)
• David Matejcek (OmniFish)
• James Perkins (Red Hat)
• Ivar Grimstad (Eclipse Foundation)
• Brian Stansberry (Red Hat)
• John Clingan (Red Hat)
• Emily Jiang (IBM)
• Dmitry Kornilov (Oracle)
• Scott Marlow (Red Hat)
• Petr Aubrecht (Payara)
• Kenji kazumura (Fujitsu)
• Cesar Hernandez (Tomitribe)
• Jan Westerkamp (iJUG)

Agenda and Minutes

Jakarta EE 11 Release Plan

• Wave 1 - 4 release review initiated by 2024-02-29 (leap day) and M2
  • Spec projects
    • 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/
      • Jakarta Activation*
        • Lukas
        • Staged: https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/activation/jakarta.activation-api/2.1.3/
      • 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/
    • Jakarta Annotations 3.0*
      • Lukas (see below)
      • Staged: https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/annotation/jakarta.annotation-api/3.0.0/
    • Jakarta Expression Language 6.0*
      • RC1 in Maven Central: https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/el/jakarta.el-api/6.0.0-RC1/
    • Jakarta Interceptors 2.2*
      • Scott Stark
      • Staged: https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/interceptor/jakarta.interceptor-api/2.2.0/
    • Jakarta Lang Model 4.1
      • (Part of CDI) Scott Stark
    • Jakarta Contexts and Dependency Injection 4.1*
      • Scott Stark
      • TCK is being finalized next couple of days
      • Waiting on EL 6.0.0 final staging to be able to stage CDI 4.1.0 final
      • DONE: Ed to ensure Mark Thomas is aware that CDI is depending on this artifact.
  • 2024-02-29 and M2 actions
    • Ed, Ivar, Arjan
      • Outstanding spec text changes
        • Placeholders for any pending changes for EE 11.
        • Put this on the spec page.
      • 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.
    • Scott
      • Ed sought an update on the parts of the CDI spec that would have been in CDI EE, but are now in the platform spec.
        • https://github.com/jakartaee/platform/pull/838
        • Scott surfaced some Eclipse Committer Agreement challenges that are preventing commits from being merged.
          • PR was flagged red because there are individuals on the PR that do not have ECA.
          • Exceptions have been approved in the past.
        • DONE: Ivar and/or Emily to bring this up at Spec Committee on 2024-03-05.
        • JEA-334: Ed to review PR with normal process and ignore ECA related failed checks.
• 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
    • 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.

        • NO LONGER NEEDED: Ed to submit a PR to https://github.com/jakartaee/platform/blob/gh-pages/jakartaee11/JakartaEE11ReleasePlan.md
      • Arjan brings a bit of retrospective comment about how we have arrived at a situation where REST, which is a core and very important spec, has very little user-level features to talk about for EE 11. Capture this for EE.next.
        • Its governance structure is different from other projects. This may be a factor.
        • Some of these are being addressed. https://www.eclipse.org/lists/rest-dev/msg00254.html
        • The “veto” aspect may need to be revisited.
    • Jakarta Server Pages*
      • Mark Thomas and Paul A. Nicolucci
    • Jakarta Servlet*
      • Mark Thomas
      • M2 is published to Maven Central today
    • 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 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
    • 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-328
• Individual specification TCK requirements for specs getting major/minor updates in EE 11
  • As of Emily’s email on 2024-02-21, it looks like this issue is resolved. Does anything else remain to be done on this one?
    • Scott Marlow asked a followup question last night:
      • Is the described behavior of the "Type 3" meant to say that all EE features are portable to (non-EE) Java SE implementations? I don't believe so but I am trying to understand if type 3 is specifically talking about the subset of TCK tests that have no EE dependencies?
      • DONE: Ed to reply and state that we discussed this in the platform call, but we believe the TCK process document needs more clarity.
    • [Brian] My final question on my email is still open: “7) Are the spec groups producing major/minor releases aware of these requirements? Where do things stand?”
      • JEA-337: Ed to ensure spec project leads for Waves 5 - 8 are aware.
• Platform integration related issues
  • When one migrates code from another Jakarta repository to the platform repo and it contains history, and authors, these are flagged as violating the contributor agreement because they are not platform committers, or historic project committers before Jakarta. The ECA is a global thing is it not?
  • The ‘@’author tagging capability does not work across repositories. If I try to tag a CDI contributor when creating/discussing a cdi-ee-tck label, their github id does not popup as it would in a CDI repo. All Jakarta contributors should be known to the platform repos in some form.