Add Automatic-Module-Name for Java 9 compatibility#11
Merged
Conversation
Contributor
|
@tomtung could you please publish a version with this fix included (either as a full release or as a snapshot). Thanks! |
Owner
|
Oops sorry forgot about this. Just published a newer version. |
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
3 participants
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 adds an
Automatic-Module-Nameto the JAR manifests, allowing the library to be used on the Java 9 module path.If the library was used before on the Java 9 module path, the module name was derived from the filename of the JAR at runtime to
latex2unicode.2.12, which is not a valid Java identifier.Latex2unicode is compatible with Java 9 when the dependency on fastparse was updated to a version where com-lihaoyi/fastparse#185 is included.
Closes #10