You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Dennis Lundberg (JIRA)" <ji...@codehaus.org> on 2011/02/03 22:16:22 UTC

[jira] Closed: (MASSEMBLY-381) Classpath entry of MANIFEST breaks jar filenames

     [ http://jira.codehaus.org/browse/MASSEMBLY-381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dennis Lundberg closed MASSEMBLY-381.
-------------------------------------

    Resolution: Not A Bug

The attached manifest is correct according to the JAR specification:

"No line may be longer than 72 bytes (not characters), in its UTF8-encoded form. If a value would make the initial line longer than this, it should be continued on extra lines (each starting with a single SPACE)."

See http://download.oracle.com/javase/1.4.2/docs/guide/jar/jar.html#Notes%20on%20Manifest%20and%20Signature%20Files

> Classpath entry of MANIFEST breaks jar filenames
> ------------------------------------------------
>
>                 Key: MASSEMBLY-381
>                 URL: http://jira.codehaus.org/browse/MASSEMBLY-381
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Bug
>            Reporter: Alexander
>         Attachments: MANIFEST.MF
>
>
> See attached MANIFEST for an example.
> Solution: Add each jar file on a newline, and rename jar files which are longer than 72 chars.

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