Use maven.compiler.release to control build targets under Java 9 and newer
#28
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@jchambers Appreciate your quick response to this issue. When can we expect the next release? |
Probably this weekend. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This fixes a strange but seemingly well-known issue where new
ByteBuffermethods introduced in Java 9 causeNoSuchMethodErrorsunder Java 8 and newer if class files are built with Java 9 or newer. The strategy here is to use the old source/target properties under Java 8 and older and the newmaven.compiler.releaseunder Java 9 and newer.This fixes #27.