Java 25 Support

[stokpop]

Java 25 just got released, which is the new LTS version.

Can we have a buildpack with Java 25? Would be great to check the performance improvements and the fix for Virtual Thread pinning.

[stokpop]

Looks like we first need a release of Java 25 on https://docs.bell-sw.com/liberica-jdk/?
(update: the release is there: https://docs.bell-sw.com/liberica-jdk/25b37/, but in pull request #1122 it seems we need a package in the buildpack distribution repo as well, who can add that?)

[bothapn]

https://docs.bell-sw.com/liberica-jdk/25.0.1b11/general/release-notes/

It looks like the new Liberica build has been finalized.

[boisvertmathieu]

Hello team,
I'm interested in helping move this forward. I assume the blocker is the availability of the JDK 25 binaries in the upstream buildpack dependency repo?
I have started looking into this on the java-buildpack-dependency-builder side:

• Issue: Add support for Java 25 java-buildpack-dependency-builder#79
• PR : Add Java 25 support java-buildpack-dependency-builder#80

If i'm not mistaken, once the artifacts are built and published there, we should be able to proceed with merging the support here?

[maecval]

@ramonskie
Can you provide information when Java 25 will be included?
We would love to have this available.

[krismarc]

@maecval #1122 (comment)

[ramonskie]

with the new 5.x release all dependencies are now updated.
please reopen if needed

[krismarc]

I'm not fully convinced if this one should be really blocked by the GO migration. It's been over 6 months since this issue was raised. V5 struggles with some early days issues and who knows when it will became a default in cf-deployment cloudfoundry/cf-deployment#1333

In some situations, it might be still next few months before it appears in some environments. Shouldn't this be re-evaluated?

[ramonskie]

all the automation for the 4.x java-buildpack does not exist anymore. since this was the only buildpack that was not actively maintained by the foundation but by pivotal>vmware>broadcom.
so even if we want to add it. there is no way we can make a release. without putting allot of effort in to it.

that is why we made such a huge effort to migrate to go/libbuildpack
the first bosh releases are out. and we are trying to have a more stable buildpack in the next coming month.
allot of teams from several companies are now actively working on getting there products live with 5.x
and we hope that the upcoming 5.1 in the next coming month will be released.
which will mark it as a stable release that is used in production everywhere

[krismarc]

from the linked issue cloudfoundry/cf-deployment#1333:

If the buildpack team releases a buildpack version this will automatically go into the cf deployment release after a successful CATS validation. Consumers can still define in their app manifest the former java-buildpack version 4.77.0