Fix running/testing Gradle projects on contemporary versions of Java #179
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
There is still a need for adjusting how Gradle projects will optimally be invoked. After adjusting the Gradle project incantation procedure recently,
cratedb-examples
was observing a regression on its Gradle project(s).gradle wrapper
, or not. pyveci/pueblo#37The new heuristics in
ngr
will wipe an existing Gradle wrapper and generate a new one, when thegradle
program is installed on the machine. This accomodates running on contemporary versions of Java, which will otherwise fail likeUnsupported class file major version 65
.gradlew
Gradle wrapper pyveci/pueblo#38References