[ http://jira.codehaus.org/browse/MJAR-39?page=comments#action_67418 ]
Jerome Lacoste commented on MJAR-39: ------------------------------------ > To do that, the lines after the first must be preceeded with a single space > – > not any whitespace, but only a single space character. – The spec says: value: SPACE *otherchar newline *continuation continuation: SPACE *otherchar newline otherchar: any UTF-8 character except NUL, CR and LF otherchar doesn't exclude SPACE and I believe space is a valid UTF-8 character. So according to my understanding, a continuation might start with more than one space. What is invalid is an empty line in the wrong place. The fact that every continuation line starts with a space guarantees that a continuation line won't be mistaken into an "fully blank line". Now it is true that in maven 2.0.4 (which uses plexus-archiver 1.0-alpha-3) there's an issue. Continuations were wrongly identified and the example <description> you posted would result in a broken Manifest. So I would like to see whether the problems still appears if you force the use of a later plexus-archiver (at least version 1.0-alpha-6). I haven't had time to look into your latest test case. > 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, MJAR-39.patch, Multiline > Manifest Value Bug Tester 2.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
