Skip to content

fix: added Automatic-Module-Name to MANIFEST.MF #526

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 2, 2022

Conversation

duponter
Copy link

When the Automatic-Module-Name entry is not added to the jar's
manifest file, Maven issues a warning during the compilation of a
project that uses that jar.

Maven issues following warning:
"Required filename-based automodules detected: [msal4j-1.13.0.jar].
Please don't publish this project to a public artifact repository!"

Currently, only a warning is generated. However, this might cause
problems in the future, especially when a project embraces the
Java Platform Module System (JPMS).

Fixes #525

When the Automatic-Module-Name entry is not added to the jar's
manifest file, Maven issues a warning during the compilation of a
project that uses that jar.

Maven issues following warning:
"Required filename-based automodules detected: [msal4j-1.13.0.jar].
Please don't publish this project to a public artifact repository!"

Currently, only a warning is generated. However, this might cause
problems in the future, especially when a project embraces the
Java Platform Module System (JPMS).
@siddhijain siddhijain merged commit 5fd90f6 into AzureAD:dev Aug 2, 2022
@duponter duponter deleted the Issue_525 branch August 2, 2022 15:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Maven Warning: Required filename-based automodules detected
2 participants