jira-importer commented on issue #225: URL: https://github.com/apache/maven-jar-plugin/issues/225#issuecomment-2956682927
**[Steven Coco](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=steevcoco)** commented Hi folks. Thanks for looking into all this. I really would like to stress that thes attributes should not be forced into the manifest. They must be defeatable. One can see it make sense liberally re-using these attributes in an enterprise environment. But in any kind of project that does not have and follow an externally-defined specification, these do not make any sense. For instance, in a standalone application, these attributes are their own kind of ludacris. A new user will also be confounded to find a specification for providing appropriate values for these does not exist. And here comes JSR-277 (http://jcp.org/en/jsr/detail?id=277), which is defining a module and versioning specification for Java You might also note that you can include a Main-Class attribute in the mainfest and still be forced into having the extension attributes; and in such a manifest configuration, the main class is supposed to be the extension's installer program. And in general, who knows what the plugin (the Java browser plugin) or Java Web Start might do with these Jars with extension specifications: which are not well-defined by the Jar author. For myself: these are going to fully cripple Maven's Jar packaging. I have to twiddle every manifest into shape before putting any Jar in service. And I would extend these comments to the War plugin. And on the subject of making a patch: I got a ways into dropping the needed sources from SVN. But AbstractJarMojo is importing org.codehaus.plexus.archiver.jar.JarArchiver which does not appear to get resolved by any of the dependencies declared in the POMs. I couldn't figure out how the classpath was supposed to be set up. Thanks again! -- 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]
