Correct project setup and documentation - #310
Merged
Merged
Conversation
…lding Co-authored-by: chrjohn <6644028+chrjohn@users.noreply.github.com>
Remove multi-release JAR (MRJAR) support; require JDK 11
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
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.
Fixes #303
As stated in #115 and #124 this project is built using JDK 11.
However, the doc and pom did not reflect this. This PR fixes that.
Removes all MRJAR artifacts — the project no longer needs to support Java 8 / pre-JPMS runtimes and JDK 11 is the sole build target.
Changes
pom.xml: Drop<Multi-Release>true</Multi-Release>frommaven-jar-pluginmanifest entriesrepository-util/pom.xml: Drop<Multi-Release>true</Multi-Release>frommaven-assembly-pluginmanifest entriesrepository/README.md,repository-util/README.md: Replace MRJAR build description with a single statement that JDK 11 is used for building