Skip to content

Java 25 Support #1121

Closed
Closed

Description

@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.

Activity

  1. stokpop commented on Sep 17, 2025

    @stokpop
    ContributorAuthor

    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?)

  2. bothapn commented on Oct 28, 2025

    @bothapn

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

    It looks like the new Liberica build has been finalized.

  3. boisvertmathieu commented on Dec 7, 2025

    @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:

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

  4. maecval commented on Mar 26, 2026

    @maecval

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

  5. krismarc commented on Mar 26, 2026

    @krismarc
  6. ramonskie commented on Mar 31, 2026

    @ramonskie
    Contributor

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

  7. krismarc commented on Apr 30, 2026

    @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?

  8. ramonskie commented on Apr 30, 2026

    @ramonskie
    Contributor

    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

  9. krismarc commented on May 5, 2026

    @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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions