Use a parent pom to ease management and release#195
Merged
Conversation
This is necessary to pick up the parent pom between releases.
The parent config for compiler plugin on Java 9+ sets release=8, but we want to leave it unset for the compile to access Unsafe appropriate to the current JDK level.
jffi still runs tests via ant so we need to set up the test JDK separately.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The JNR projects have traditionally been released and managed separately, but they are very interconnected and frequently released at the same time. This PR moves to a common parent POM (managed in https://github.com/jnr/parent) to simplify plugin management and releasing.