[ http://jira.codehaus.org/browse/MNG-1558?page=comments#action_51923 ]
Zeger Hendrikse commented on MNG-1558: -------------------------------------- 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 )-: > Manifest generation problems caused by valid POM information > ------------------------------------------------------------ > > Key: MNG-1558 > URL: http://jira.codehaus.org/browse/MNG-1558 > Project: Maven 2 > Type: Bug > Components: maven-jar-plugin > Versions: 2.0 > Reporter: Bob Allison > Fix For: 2.0.1 > > > It looks like we have some problems with the contents of manifests in jar > files. > According to Sun's documentation > (http://java.sun.com/j2se/1.5.0/docs/guide/jar/jar.html), there are three > basic formatting rules which are not always being enforced: > 1) All text must be UTF-8 > 2) Lines are limited to 72 characters; longer lines must be continued > 3) Sections are divided by blank lines > Where are these rules being violated? The first rule can be violated by any > POM which is in a character set other than UTF-8. The last two rules can be > violated by any POM value which spans multiple lines. Both of these are > potential problems since a number of POM values go directly into the manifest > without sufficient checking. > > > Example: > The plugin I have been working on suddenly stopped working. It stopped when > I added a two-line description to the POM. I have been able to determine > that converting the second line of the description into a proper manifest > continuation line fixed the problem. As it turns out, the class loader was > ignoring the jar; this created an error where the name of the Mojo class was > found but the class could not be loaded. > Workarounds for the present: > -- Any POM fields which end up in a jar manifest needs to be limited to > UTF-8 characters. > -- Multi-line values should be constructed so that all lines start with a > space character (not strictly required for the first line but it doesn't > hurt). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
