[ 
http://jira.codehaus.org/browse/MNG-2542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116878
 ] 

Olivier Lamy commented on MNG-2542:
-----------------------------------

But If I correctly read 
http://java.sun.com/j2se/1.3/docs/guide/jar/jar.html#Name-Value%20pairs%20and%20Sections
I don't see why tab in value should be exclude.

  section:                       *header +newline
  nonempty-section:      +header +newline
  newline:                      CR LF | LF | CR (not followed by LF)
  header:                       name : value
  name:                         alphanum *headerchar
  value:                          SPACE *otherchar newline *continuation
  continuation:              SPACE *otherchar newline
  alphanum:                  {A-Z} | {a-z} | {0-9}
  headerchar:                alphanum | - | _
  otherchar:                  any UTF-8 character except NUL, CR and LF

Concerning CR is related to PLX-185.

> Remove carriage returns and tabs from field values in the manifest file
> -----------------------------------------------------------------------
>
>                 Key: MNG-2542
>                 URL: http://jira.codehaus.org/browse/MNG-2542
>             Project: Maven 2
>          Issue Type: Bug
>          Components: maven-archiver
>    Affects Versions: 2.0.4
>            Reporter: Tim O'Brien
>             Fix For: Shared Components
>
>
> When creating a JAR Manfiest, maven needs to remove CR and Tabs from the 
> description taken from the POM.  
> This is a critical issue with JAR files created from Maven.  The issue is 
> that Maven can create a MANIFEST file for a JAR, but it creates an invalid 
> manifest if you jsut happen to have a description in your POM like thi:
> <description>
>     this is an library for idiots
> </description>
> The issue is that your description element has new line characters and thejar 
> plugin just take those new line characters and blindly copies them into the 
> Manfiest, creating an invalid Manifest.   This doesn't show up until you try 
> to use the JAR in another application.  Then you get a very cryptic error 
> message about having an invalid jar.
> This used to be 1247 but it was closed and marked as Won't Fix with no 
> explanation as to why it isn't worth fixing.    

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