You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears that MANIFEST.MF doesn't provide the Automatic-Module-Name attribute which makes the library difficult to use with the Java module system.
Without it, the name of the module in a requires directive would be the name of the JAR file which is subject to change leading to compile and runtime issues.
Would it be possible to include this in the build using something like this:
In the long run it would be better to convert the library to a Java module by defining a proper module-info.java but the attribute should be enough for now.
Regards
The text was updated successfully, but these errors were encountered:
Hi,
It appears that
MANIFEST.MF
doesn't provide theAutomatic-Module-Name
attribute which makes the library difficult to use with the Java module system.Without it, the name of the module in a
requires
directive would be the name of the JAR file which is subject to change leading to compile and runtime issues.Would it be possible to include this in the build using something like this:
In the long run it would be better to convert the library to a Java module by defining a proper
module-info.java
but the attribute should be enough for now.Regards
The text was updated successfully, but these errors were encountered: