Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[] Jakarta EE Spec Committee Approved Meeting Minutes - February 9th, 2022

Jakarta EE Spec Committee - February 9th, 2022

Attendees (present in bold):

Kenji Kazumura - Fujitsu

Tom Watson - IBM - Emily Jiang

Ed Bratt - Oracle - Dmitry Kornilov

Andrew Pielage - Payara

David Blevins - Tomitribe - Jean-Louis Monteiro, Cesar Hernandez

Ivar Grimstad - PMC Representative

Marcelo Ancelmo - Participant Member - Martijn Verburg

Werner Keil - Committer Member

Jun Qian - Primeton - Enterprise Member

Zhai Luchao -  Shandong Cvicse Middleware Co. - Enterprise Member


Eclipse Foundation: Tanja Obradovic, Paul Buck (chair)

Guests: Scott Stark, Scott Marlow

Past business / action items:

  • Approval is requested for the meeting minutes from the January 26th, 2022 meeting as drafted - Approved.


  • Ongoing tracking spreadsheet of individual specs progressing through the JESP

  • Follow-up on namespace action items from January 26th call:

    • 1.There was  confusion around what was decided regarding TCK package names and how it is to be applied to spec projects in Jakarta EE 10, and subsequent releases was not provided

      • Action: Package namespace decision is for future releases. Proposed draft text from Emily:

        • 1. The usage of jakarta.* as Jakarta EE TCK package names is NOT permitted in any of Jakarta EE releases. If some TCK tests use jakarta.* namespace, they can easily be challenged as invalid because jakarta.* was reserved for Jakarta EE API usage only. The challenge would be valid and the risk of getting the TCKs excluded would be very high.

        • 2. If a newly written Jakarta EE 10 TCK uses jakarta.*, they MUST be renamed.

        • 3. The recently approved TCK package name ee.jakarta.tck.[spec] can be used by Jakarta EE TCKs but the usage is not required. The project team can choose other TCK package names if they wish.

No further review or discussion required. The “official” communication is the JESP and the TCK Operations Guide.

Reviewed, no objections, +1 to the PR from the Spec Committee

  • 3. General guidance on the authorized usage of the jakarta package namespace governed by the Eclipse Foundation and the Working Group

    • Action: Write down somewhere that the jakarta namespace is for APIs of Jakarta specifications. Update the JESP and add boilerplate to all the specification documents. See PR for proposed update from Ivar:

Reviewed, no objections noted, as per JESP 7 day ballot to be initiated

This matter is closed, ratification spec can be done with RC.

The following item were not covered and will be added to the agenda for next meeting

Back to the top