ngr: Fix Gradle test runner by wiping existing gradlew
Gradle wrapper
#38
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.
About
Fixing ngr's Gradle outlet once more aims to accommodate for contemporary versions of Java, where older versions of shipped Gradle wrappers would fail on:
Unsupported class file major version 65
and friends.Coming from GH-37, this patch attempts to resolve the problem by trying another heuristic, which will prefer wiping an existing
gradlew
wrapper script, if there is a chance that a new one can be generated, i.e. when thegradle
program is installed on the system.Otherwise, ngr will emit a corresponding error message:
Testdrive