Reinstate Gradle support for heroku/buildpacks:{18,20}
#264
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
heroku/java
previously supported Gradle by mixing in the shimmedheroku/gradle
buildpack. When we decided to make a clean cut and not have shimmed buildpacks in the CNB repository, support for Gradle inheroku/java
was dropped.This is obviously a major breaking change and this PR reinstates Gradle support by mirroring the order definition that was previously in
heroku/java
. This is not a complete fix since users that explicitly usedheroku/java
(i.e.--buildpack heroku/java
withpack
) will still get detection failures for Gradle. However, using the builder without explicit buildpacks will work fine for Gradle projects.Closes GUS-W-11298364