Added Automatic-Module-Name to jar manifests for Modular Java #1635
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.
Checklist
main
branch.Reference/Link to the issue solved with this PR (if any)
Description of the problem
I am building Modular Java 18 apps. When I add one or more of these libraries, it breaks my build because the library does not have a module that I can import.
Description of the solution
By adding the Automatic-Module-Name to the jar Manifest, people writing modular Java will still be able to use the libraries without preventing those still on Java 8 from using them. I have made this change in other Azure projects to allow Modular support.
*No tests changes were made, because the changes to the build file should not affect the code, only adding a line to the manifests that will allow them to work with Modular Java.