The Jakarta EE Platform Project has provided the following motivation for the changes:
This change allows for several things while not restricting anything.
- It allows compatible runtimes to certify on Java SE 17 OR 21, while simultaneously allowing Concurrency to provide Java SE version runtime-aware support for Virtual Threads.
- It allows users who are not at liberty to run Java SE 21 to adopt Jakarta EE 11.
- It allows us to keep our delivery schedule of June/July 2024 to complete Jakarta EE 11.
Per the process, this will be a fourteen-day ballot, ending on
Tuesday, February 13, 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. According to the process, the ballot will conclude at the earliest on Tuesday, February 6 when all members have cast their vote.
The Specification Committee is composed of representatives of the Jakarta EE Working Group Member Companies (Fujitsu, IBM, Oracle, Payara, Tomitribe, Primeton Information Technologies, and Shandong Cvicse Middleware Co.), along with individuals who represent the EE4J PMC, Participant Members, and Committer Members.
