java buildpack 5.+

[krismarc]

Do we know any timeline for enabling java buildpack 5.+?

[oliver-heinrich]

hi,
we released the new java buildpack 5.+ with https://github.com/cloudfoundry/cf-deployment/releases/tag/v56.0.0

[krismarc]

my understanding from this cloudfoundry/java-buildpack#1121 (comment) is that the version 5.1+ is going to be considered stable, therefore, I'm not sure if going with 5.0.1 is the right move

[oliver-heinrich]

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

[krismarc]

no if you are in air-gaped environment and you're using default buildpacks shipped with cf-deployment

[oliver-heinrich]

Hi @krismarc if you are talking about air-gapped I assume you are within SAP. Please note, that we 'pin' for cf v56.0 the java-buildpack release still on version 4.77.0 inside SAP ..means we will switch later to the new Java Buildpack version 5.X. for compatibility reasons.
Please let us discuss SAP internals in internal communication tools.
Does this help?

[krismarc]

nop, I'm not SAP. We use third-party cloud service based on CF. I'm planning to ask our vendor to do the same and we will keep like that till early days problems are gone and probably once we switch, we will keep old one named differently as potential rollback option (to avoid switching back and forth).

[oliver-heinrich]

Hi @krismarc, we are also consumers of the cf community releases and have to ensure stability.

Our approach is to 'pin/replace' the system java_buildpack of the cf community release back to the old version 4.77.0 and
add version 5.0.1 and higher 5.X versions as additional buildpack with the name 'java_buildpack_v5_preview', so that
consumers can tests their cf apps on the new version.

java_buildpack - 4.77.0
java_buildpack_v5_preview - buildpack 5.0.X or higher 5.X

After a while we switch then v5.X to the system buildpack 'java_buildpack'.

Maybe this is an option for your vendor as well.

[krismarc]

Exactly, that’s our plan then.

[ramonskie]

even if it is airgapped you could still make a offline buildpack from the latest release and upload that to CF

[krismarc]

even if it is airgapped you could still make a offline buildpack from the latest release and upload that to CF

yes, I know, and this leads us to this discussion: cloudfoundry/java-buildpack#1224 😄