You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Also, the 4.x branch was done before @pivotal-david-osullivan or I started working on the project and we have no context on the changes there. Why it was done, what advantages it has over 3.x, why did the cli flags change, etc... Since there's no context on the project anymore, we'd have to do a pretty extensive code and commit review before doing anything with it.
Is there something you are looking for that is in the 4.x branch but not in 3.x?
@dmikusa seems like go version of the buildpack is going to use 4.2 version. That's not really mentioned in the comparison.
Actually, the version 4.2 was never officially released in github https://github.com/cloudfoundry/java-buildpack-memory-calculator, the last version is 4.1 and there's just a branch for 4.2
..I'm actually looking for alternative source for building an offline version of the buildpack
Activity
mayrstefan commentedon Feb 22, 2023
Okay, I see they use different cli parameters which is a breaking change. Are there any plans for an upgrade?
dmikusa commentedon Mar 6, 2023
Yes, that is a reason.
Also, the 4.x branch was done before @pivotal-david-osullivan or I started working on the project and we have no context on the changes there. Why it was done, what advantages it has over 3.x, why did the cli flags change, etc... Since there's no context on the project anymore, we'd have to do a pretty extensive code and commit review before doing anything with it.
Is there something you are looking for that is in the 4.x branch but not in 3.x?
mayrstefan commentedon Mar 6, 2023
I was just wondering what is going here. Also I found a reference to version 4.1 when looking around the Tanzu buildpack docs: https://docs.vmware.com/en/VMware-Tanzu-Buildpacks/services/tanzu-buildpacks/GUID-release-notes-graalvm-release-notes.html. Surprisingly this is only mentioned as a dependency in old versions of the GraalsVM buildpack. For paketo buildpacks the memory calculatore now seems to be part of the runtimes via a go dependency. We can find the calculator in https://github.com/paketo-buildpacks/libjvm/tree/main/calc
Maybe @nebhale can tell us what was the reason for the changes of the memory calculator
krismarc commentedon Mar 26, 2026
@dmikusa seems like go version of the buildpack is going to use 4.2 version. That's not really mentioned in the comparison.
Actually, the version 4.2 was never officially released in github https://github.com/cloudfoundry/java-buildpack-memory-calculator, the last version is 4.1 and there's just a branch for 4.2
..I'm actually looking for alternative source for building an offline version of the buildpack
ramonskie commentedon Apr 24, 2026
@krismarc the go based java-buildpack now supports selective profiles for creating offline buildpacks. see #1228
ramonskie commentedon May 20, 2026
5.x now uses memory calculator v4