[jakarta.ee-spec] Jakarta EE Spec Committee Approved Meeting Minutes - J

[Andrew Pielage <andrew.pielage@xxxxxxxxxxx>]

Jakarta EE Spec Committee - January 8th, 2025

Attendees (present in bold):

Kenji Kazumura - Fujitsu

Emily Jiang - IBM - Tom Watson

Ed Bratt - Oracle - Dmitry Kornilov

Andrew Pielage (chair)  - Payara - Petr Aubrecht

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

Ivar Grimstad - PMC Representative

Marcelo Ancelmo - Participant Member -  Abraham Marin-Perez

Werner Keil - Committer Member

Jun Qian - Primeton Information Technologies - Enterprise Member

Zhai Luchao -  Shandong Cvicse Middleware Co. - Enterprise Member

Guest - Jakarta EE 11 co-release coordinators: Ed Burns, Jared Anderson

 

Eclipse Foundation: Tanja Obradovic

Past business / action items:

• Approval is requested for the minutes from the November 27th, 2024 meeting as drafted - Approved
• Approval is requested for the minutes from the December 11th, 2024 meeting as drafted - Approved

Agenda:

• Ongoing tracking spreadsheet of specifications progressing through the JESP specification version lifecycle
• Check in on EE 11 Release Review ballots, see the spreadsheet for updates and notes.
• Request to publish the Core Profile TCK zip and then extract and publish the individual JAR artifacts afterwards (no vote required - approved by those in call):  https://github.com/jakartaee/specifications/pull/782#issuecomment-2575717225 
• Web Profile TCK to be published ahead of Platform
• TCK user guide being worked on, which will apply to both Web Profile and Platform
• ETA on ballot date by next call
• An approach to unblock the remaining persistence tests for the Platform TCK has been found
• No exact ETA right now, Q1 target possible
• ~6500 tests blocked (app client performing an EJB lookup), suggested change is to use the Servlet vehicle instead of Remote EJB.
• Catch up on the Jakarta EE 11 Release Plan [Ed Burns]
• EE 11 - Prioritized backlog · Jakarta EE11 TCK Release (github.com) and Jakarta EE11 TCK Release board  
• Catch up on the Jakarta EE 12 Release Plan [Ed Burns]
• Reza drafted an action plan
• EE 12 label to be applied to the issues
• Check on Progress Reviews for:
• Jakarta NoSQL 
• https://jakarta.ee/specifications/nosql/
• https://www.eclipse.org/lists/jakarta.ee-spec/msg02795.html [Progress Review, 10.2022]
• Issue for progress review created: https://github.com/jakartaee/nosql/issues/185
• Some activity on the issue, finishing off the TCK
• Jakarta Config 
• https://jakarta.ee/specifications/config/
• https://www.eclipse.org/lists/jakarta.ee-spec/msg02838.html [Plan Review, 01.2023]
• Issue for progress review created: https://github.com/jakartaee/config/issues/277 
• No update yet
• Jakarta RPC 
• https://jakarta.ee/specifications/rpc/
• https://www.eclipse.org/lists/jakarta.ee-spec/msg02129.html [Creation Review, 01.2022]
• Issue for progress/plan review created: https://github.com/jakartaee/rpc/issues/3 
• No update yet
• Check on Creation Review for Jakarta Logging
• Emailed today
• Issue #55
• Check in on Ed Bratt’s document: link
• Check in on Ed Bratt’s PR: pending
• Issue #74
• Email being drafted
• Issue #58
• This is not strictly with Emily, pull requests using the template just need to be made
• Issue #81
• No issues found - can proceed
• Review other open issues:
• Determine which issues to label as “enhancement” and add to our board
• Close issues which are no longer relevant or have been dealt with
• Clean up and clarify how to list TCK service releases on spec pages
• Varied usages
• Some specs only link to the latest service release: https://jakarta.ee/specifications/cdi/4.0/ 
• Others link to all: https://jakarta.ee/specifications/authentication/3.1/ 
• Some have a text explaining what the service release is for: https://jakarta.ee/specifications/servlet/6.1/ 
• All TCKs versions are valid
• Discussion about keeping the compatible implementations list updated:
• TCK process already covers this: “... if there is already at least one certified compatible implementation before the challenge, the new, modified TCK should be run against at least one such implementation (and ideally all of them) before the changes are published, released, and finalized. If such a change were released, and it was later found to cause a previously-certified implementation to fail the new, modified test, then excluding the test would likely be the only option, and this would require yet another, additional service release.”
• Suggestion:
• Add an extra bullet point with text along the lines of “For all TCK releases, see download directory here)” and link to the download directory for that version of the specification (e.g. https://download.eclipse.org/jakartaee/servlet/6.1/)
• Extra suggestion: only add this text once there has been a service release made?

--

Andrew Pielage
Senior Software Engineer

		payara.fish
		+448005385490

Try our fully managed cloud native application runtime. 15 day trial available. Payara.cloud

Payara Services Ltd, Registered office: Malvern Hills Science Park, Geraldine Road, Malvern, WR14 3SZ, United Kingdom
Registered in England and Wales: 09998946 | VAT: GB 193854467

Payara is a proud recipient of the prestigious Queen's Award for Enterprise: International Trade 2021