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
without a jar specifying a module name or having a module-info JPMS will use the jar name as an automatic module. For some users this will be fine but for library projects that publish to maven repositories this is not ok. Hence seeing warning messages like this:
* Required filename-based automodules detected: [moshi-1.14.0.jar]. Please don't publish this project to a public artifact repository! *
personally I would much have a world where everything in maven central contained a module-info.java but at least specifying the Automatic-Module-Name in the jar's manifest would be beneficial.
The text was updated successfully, but these errors were encountered:
without a jar specifying a module name or having a module-info JPMS will use the jar name as an automatic module. For some users this will be fine but for library projects that publish to maven repositories this is not ok. Hence seeing warning messages like this:
personally I would much have a world where everything in maven central contained a module-info.java but at least specifying the Automatic-Module-Name in the jar's manifest would be beneficial.
The text was updated successfully, but these errors were encountered: