The TCK Release Notes refers to Eclipse GlassFish as a
compatible implementation but the CCR for this ballot refers to
Apache Tomcat.
The TCK User Guide similarly refers to Eclipse GlassFish, not
Tomcat. Further, it only refers to Java SE 21 -- the TCK (based
on the CCR) runs on JDK 17 and/or 21.
There is no SHA-256 in the CCR so it is impossible to verify
the correct TCK was used
I'm okay with these issues being addressed in a micro-release
update (1 & 2). The CCR should be updated to reflect the
SHA-SUM used by the implementation team.
Thanks!
-- Ed Bratt
On 3/15/2024 3:04 AM, Andrew Pielage
via jakarta.ee-spec wrote:
Greetings
Jakarta EE Specification Committee.
I
need your vote to approve and ratify the release of Jakarta
_expression_ Language 6.0 as part of the Jakarta EE Platform 11
release.
The
JESP/EFSP requires a successful ballot of the Specification
Committee in order to ratify the products of this release as a
Final Specification (as that term is defined in the EFSP).
Per
the process, this will be a fourteen day ballot, ending on
29thMarch
2024 that requires a Super-majority positive vote of the
Specification Committee members (note that there is no veto).
Community input is welcome, but only votes cast by
Specification Committee Representatives will be counted.
The
Specification Committee is composed of representatives of the
Jakarta EE Working Group Member Companies (Fujitsu, IBM,
Oracle, Payara, Tomitribe, Primeton, and Shandong Cvicse
Middleware Co.), along with individuals who represent the EE4J
PMC, Participant Members, and Committer Members.
Specification
Committee representatives, your vote is hereby requested.
Please respond with +1 (positive), 0 (abstain), or -1
(reject). Any feedback that you can provide to support your
vote will be appreciated.