jira-importer commented on issue #148: URL: https://github.com/apache/maven-jar-plugin/issues/148#issuecomment-2956672845
**[Zeger Hendrikse](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=tushen)** commented We (at Fortis bank) are seriously hampered by this issue as well. - Trying to let Maven add entries to the manifest by specifying \<addMavenDescriptor>false\</addMavenDescriptor> results in a null-pointer exception - Specifying \<Specification-Title> ourselves in the jar plug-in configuration results in a multiple specification error - Concatenating the content of the description element in the POM to one line only, results in a Specification-Title entry in the manifest that is broken up at 72 chars (as it should by the spec), but which makes the WARs and JARS undeployable on the application server (WPS 5.1.0.1) We concluded, it should either be possible to - Specify your own manifest file in the JAR plug-in (and not let Maven append the contents of your private manifest file to the one generated by Maven itself, as it seems to do currently) - Be able to switch on/off all separate attributes of the manifest generation - Don't put the contents of the description element in the POM in the Specification-Title entry in the manifest. If the length cannot be more than 72 chars, what would be the added value of the description in the POM? Currently we see ourselves forced to abbreviate all the descriptions to 72-"Specification-Title".length() characters, but this doesn't result in a nice entry page in the Maven site generated pages )-: -- 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]
