[ 
http://jira.codehaus.org/browse/MJAR-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=196527#action_196527
 ] 

Thorsten Möller commented on MJAR-96:
-------------------------------------

Well, at the time I spotted this issue (more than one year ago) my 
configuration most probably was WinXP SP2, Java 1.5.14(?), Maven 2.0.9, and the 
latest jar plugin released at that time.

I can't verify it any better today because I don't use the maven 
retrotranslator plugin anymore. However, checking if this bug still exists with 
the recent version shouldn't be that difficult, just add a linebreak in the 
description text in a pom and see if the jar manifest will have the linebreak 
as well.

> Manifest file contains line breaks if project description tag of pom.xml is 
> not on single line
> ----------------------------------------------------------------------------------------------
>
>                 Key: MJAR-96
>                 URL: http://jira.codehaus.org/browse/MJAR-96
>             Project: Maven 2.x Jar Plugin
>          Issue Type: Bug
>         Environment: Windows. Seems that the bug does not appear on Linux.
>            Reporter: Thorsten Möller
>            Priority: Minor
>
> Consider the following pom.xml (excerpt)
> <groupId>mygroup</groupId>
> <artifactId>myartifact</artifactId>
> <version>2.0</version>
> <packaging>jar</packaging>
> <name>My Name</name>
> <description>This is the first line of my project description
> and this is another line, which is on this line because it was formated this 
> way (for whatever reason).</description>
> Such a non-single-line description ends up in the MANIFEST.MF file containing 
> line breaks. This might cause exceptions (by other tools) when the manifest 
> file is processed. In particular, the Retrotranslator Maven plugin throws a 
> IOException if it tries to write a translated JAR based on such a corrupted 
> MANIFEST file.
> Make sure, to remove line breaks that result from the XML (and other 
> whitespace) in order not to cause such (very hard to find) problems, i.e., 
> make sure that all properties in the MANIFEST.MF do not spread over multple 
> lines.

-- 
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


Reply via email to