[ http://jira.codehaus.org/browse/MJAR-39?page=comments#action_66570 ]
Jochen Wiedmann commented on MJAR-39: ------------------------------------- I wonder what a sensible solution for the problem could be. Things that come to my mind: 1.) Depend on the proposed patches for MJAR-38 and throw an Exception, if a Manifest attribute contains line feeds. (The proposed patch would allow the user to supply a different value.) 2.) Silently replace the line feeds with blanks. 3.) Reduce the problem to the special case of Specification-Title. If the <description> element contains line feeds, use the <name> element. Personally, I would clearly suggest 1.) > Maven Sets Manifest Attribute Values to Multi-Line Strings > ---------------------------------------------------------- > > Key: MJAR-39 > URL: http://jira.codehaus.org/browse/MJAR-39 > Project: Maven 2.x Jar Plugin > Type: Bug > Versions: 2.0 > Environment: Maven version: 2.0.4 > Microsoft Windows XP [Version 5.1.2600] > Reporter: Steven Coco > Attachments: Jar Specification-Title Tester.zip > > > Maven will set a Manifest attribute's value to a multi-line string, > which results in an invalid Manifest. > By default, on its own, Maven adds a Specification-Title attribute to > the Manifest, and sets its value to the POM's <description> element. If this > is a multi-line value in the POM, Maven will insert it unchanged: and yield > an invalid Manifest. Maven then can't even load the jar that it just created > itself! > I have filed another bug relating to the fact that it should not insert > such an attribute by default: MJAR-38 -- 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
