DBZ-6320 Fix Cassandra3 build to work with JDK names sans dots. #110
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.
https://issues.redhat.com/browse/DBZ-6320
The most recent JDK 20 version string is simply "20" and the jamm dependency bundled with cassandra-all does not support version strings that may not contain dots, basically it only supports JDK 8 or earlier. Bumping to 0.3.3 supports dot and non-dot named version strings.
@jpechane This should fix the Java Outreach failures with JDK20 for Cassandra builds.