desruisseaux commented on issue #520: URL: https://github.com/apache/maven-jar-plugin/issues/520#issuecomment-4712802276
Module name in `MANIFEST.MF` file is indeed a different thing that module name on `module-info.java`. As @dmlloyd said, it is a compromise created by Oracle for allowing a gradual transition for projects that are not yet able to provide a real `module-info.java`. In my understanding, the root of the problem is that a mechanism already exists in Maven 3, but it does not work well with properties. While setting module name on the command line is not something that I would like to encourage, using properties is nevertheless possible in Maven for all sort of configuration, and we could expect `MANIFEST.MF` configuration in general (including automatic module name) to work with properties too. I would like to clarify what are the impediment in using properties for configuring tħe `MANIFEST.MF` file. As said in my previous comment, I would prefer to either fix the current `<manifestEntries>` way rather than introducing a new way, or if a new way is necessary, to put it into the existing `<manifest>` element rather than creating a new element having its own independent existence. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
