Repository navigation
Ask SimRel project not to bump BREEs to Java 25 #75
Description
Executive Summary:
I suggest that the Planning Council ask the SimRel projects to hold off bumping the BREE to Java 25 until a Temurin JDK for Java 25 is supported for all supported Platforms.
The rules for when SimRel projects can start using Java 25 leave a bit of room for interpretation.
Java 25 released September 16th. The 2026-03 release is March 11:
So that isn't quite 6 months (if you consult a lawyer).
In any case, I wouldn't really care except that Temurin has yet to produce a win32 aarch64 Java 25 release:
So the JDK downloads for that are missing.
Therefore JustJ does not have such a thing either and as a result of that we would not be able to build installers and would not be able to build EPP packages for win32 aarch64 Java 25.
Activity
HeikoKlare commentedon Dec 1, 2025
Indeed. The requirements explicitly state:
This indicates to me that the idea is to have the next two releases still support the previous LTS (therefore the 6-9 months priod). In the current case, the first release to potentially use Java 25 would thus be 2026-06. Maybe my understanding is wrong and obviously the requirements are not precise enough on this, so we should definitely improve them.
In any case, I don't think that SimRel projects should be allowed to bump the BREE according to these requirements no matter what's going on around (e.g., compatibility problems with a new LTS or even the missing availability of a JDK build as we see here). That's why I agree with your opinion to ask to not bump to Java 25 for the 2026-03 release, no matter how the current requirements are interpreted.
jonahgraham commentedon Dec 1, 2025
The "26" in #75 (comment) is a typo?
merks commentedon Dec 1, 2025
Sorry, yes I edited the comment to fix it.
(For Java 26 beta we actually do have win32 aarch64 because the betas don't need to pass the TCKs.)
HeikoKlare commentedon Dec 3, 2025
The topic was discussed in today's planning council meeting, see:
To deal with the situation, the following was proposed and agreed on by the participants:
We encourage every planning council member to share their opinion and potential veto on this by Tuesday, 9th December 2025. If no concerns will be raised by then, the planning council will share this decision via the SimRel mailing list with the SimRel participants.
HeikoKlare commentedon Dec 10, 2025
As agreed, information has been sent via simrel-dev mailing list: https://www.eclipse.org/lists/simrel-dev/msg00106.html
jonahgraham commentedon Dec 11, 2025
@chirontt as you have previously contributed significantly in the past to support Windows on ARM I wanted to ensure that you saw this message as it both may affect you and perhaps you have insights on getting Windows on ARM JVMs resolved.
chirontt commentedon Dec 12, 2025
@jonahgraham Sorry, I've never been to the JDK development/testing, so I'm of no help here.
jonahgraham commentedon Dec 15, 2025
No worries @chirontt - I am glad you have seen this issue so that you are in the loop of what the project is doing with regards to this work. I hope you can continue to advocate for Windows on ARM users/developers, to whatever level you think is appropriate, so that we don't forget about them.
merks commentedon Jan 29, 2026
FYI, the latest comment here suggests that the current round of JDK updates will not include Windows aarch64 for Java 25 but that it might be available in the April cycle:
adoptium/aqa-tests#6623 (comment)
HeikoKlare commentedon Jan 29, 2026
I also came across this recent post yesterday, which confirms that timeline:
HeikoKlare commentedon Mar 5, 2026
The topic was re-discussed for the 2026-06 release in yesterday's planning council meeting, see:
Like for the 2026-03 release, we decided to ask SimRel participants not to move to Java 25 for the 2026-06 release. See the planning council's meeting minutes for additional information.
I
will sendhave sent an e-mail to the SimRel mailing list without waiting for additional feedback from planning council members that may have not attended yesterday's meeting, because the new release cycle is about to start and projects may decide to bump to Java 25 early: https://www.eclipse.org/lists/simrel-dev/msg00120.htmlHeikoKlare commentedon Jun 9, 2026
The topic was re-discussed for the 2026-09 release in last week's planning council meeting, see:
Even though there is still no Java 25 Temurin build available for Windows on ARM, we decided to not hold back Java 25 adoption any longer. We just want to have the Eclipse Platform stay at Java 21 for the next release except for specific fragments using FFM being added (while the existing fragments compatible with Java 21 stay available). See the planning council's meeting minutes for additional information.
I
will sendhave sent an e-mail to the SimRel mailing list with this information to have everyone informed about the decision: https://www.eclipse.org/lists/simrel-dev/msg00131.htmlchirontt commentedon Jun 9, 2026
@HeikoKlare
I'm curious: are there more info about this effort? GitHub issues? mailing lists? discussion groups?
HeikoKlare commentedon Jun 12, 2026
Are you interested in the actual work on this? The comment was rather meant like: "in case someone plans to work on this, it has to be done in separate fragments" without particularly knowing that/if someone wants to work on that.
I know from some people being interesting in starting work on FFM adoption but I am not sure how soon that will happen and I don't think there are any public written discussions about that yet.
akurtakov commentedon Jun 12, 2026
In chat between @merks and me after the call about what installer uses and whether (opt-in/fragment) usage of FFM in e.g. o.e.core.net/o.e.equinox.security bundles could complicate things - I have decided for myself that it's not worth the hassle now and I'll just wait for September release and try to find time to replace JNA with FFM for December release.
merks commentedon Jun 12, 2026
I think folks could start prototyping to get experience any time...
@HannesWell has asked for another status update here:
adoptium/adoptium-support#1402 (comment)
I can only hope that Temurin delivers the goods that we know and love!
I'll close this issue now since we've opened the floodgates now and EPP is prepared to run with content that requires Java 25.
chirontt commentedon Jun 15, 2026
Got it, and each on their own then. We'll discuss it further in appropriate venues when needed.
FYI, I'm experimenting with FFM for the Windows ConPTY APIs used in the Terminal plugin in the CDT project.
merks commentedon Jul 15, 2026
FYI, this iplab issue to use a Microsoft-provided JDK has been approved:
Based on that, the latest JustJ release of Java 25
now references this respin of 25.0.3 to include Windows Aarch64 JREs: