You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by ji...@codehaus.org on 2004/06/03 15:48:58 UTC
[jira] Created: (MPJAR-28) Broken Class-Path entry in manifest.mf
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPJAR-28
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPJAR-28
Summary: Broken Class-Path entry in manifest.mf
Type: Bug
Status: Open
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-jar-plugin
Assignee: Jason van Zyl
Reporter: Janne Kario
Created: Thu, 3 Jun 2004 9:47 AM
Updated: Thu, 3 Jun 2004 9:47 AM
Environment: Maven RC3, Java 1.4.2_03
Description:
Class-Path manifest entry created by the jar plugin is wrapped at 70 chars resulting in a broken manifest entry.
eg.
Class-Path: *******-common-1.0.jar *******-jms-1.0.jar ***********-ej
b-1.0.jar mx4j-jmx-2.0.1.jar mx4j-2.0.1.jar mx4j-tools-2.0.1.jar mx4j
-impl-2.0.1.jar log4j-1.2.8.jar
Each manifest entry line ends at char number 70. The next line begins with a space.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MPJAR-28) Broken Class-Path entry in manifest.mf
Posted by ji...@codehaus.org.
The following comment has been added to this issue:
Author: Dominique Jocal
Created: Thu, 3 Jun 2004 10:24 AM
Body:
We could notice that the spec does not require to 'split' the words, it only requires lines to size 72 char max. A classical word-wrapping (words not splitted) should be ok with the spec.
We observed in big projects that Manifests with cut dependencies are terrific : it's not possible any more to search for a dependency by its name, as it's potentially splitted.
Unfortunately, a correction in Maven may be difficult to do as it seems here we use an Ant feature.
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MPJAR-28?page=comments#action_20317
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPJAR-28
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPJAR-28
Summary: Broken Class-Path entry in manifest.mf
Type: Bug
Status: Open
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-jar-plugin
Assignee: Jason van Zyl
Reporter: Janne Kario
Created: Thu, 3 Jun 2004 9:47 AM
Updated: Thu, 3 Jun 2004 10:24 AM
Environment: Maven RC3, Java 1.4.2_03
Description:
Class-Path manifest entry created by the jar plugin is wrapped at 70 chars resulting in a broken manifest entry.
eg.
Class-Path: *******-common-1.0.jar *******-jms-1.0.jar ***********-ej
b-1.0.jar mx4j-jmx-2.0.1.jar mx4j-2.0.1.jar mx4j-tools-2.0.1.jar mx4j
-impl-2.0.1.jar log4j-1.2.8.jar
Each manifest entry line ends at char number 70. The next line begins with a space.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MPJAR-28) Broken Class-Path entry in manifest.mf
Posted by ji...@codehaus.org.
The following comment has been added to this issue:
Author: Janne Kario
Created: Thu, 3 Jun 2004 9:51 AM
Body:
The same thing happens with the Class-Path entry in the ejb plugin which leads me to believe that this is not an issues with JAR plugin itself.
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MPJAR-28?page=comments#action_20314
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPJAR-28
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPJAR-28
Summary: Broken Class-Path entry in manifest.mf
Type: Bug
Status: Open
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-jar-plugin
Assignee: Jason van Zyl
Reporter: Janne Kario
Created: Thu, 3 Jun 2004 9:47 AM
Updated: Thu, 3 Jun 2004 9:51 AM
Environment: Maven RC3, Java 1.4.2_03
Description:
Class-Path manifest entry created by the jar plugin is wrapped at 70 chars resulting in a broken manifest entry.
eg.
Class-Path: *******-common-1.0.jar *******-jms-1.0.jar ***********-ej
b-1.0.jar mx4j-jmx-2.0.1.jar mx4j-2.0.1.jar mx4j-tools-2.0.1.jar mx4j
-impl-2.0.1.jar log4j-1.2.8.jar
Each manifest entry line ends at char number 70. The next line begins with a space.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Closed: (MPJAR-28) Broken Class-Path entry in manifest.mf
Posted by ji...@codehaus.org.
Message:
The following issue has been closed.
Resolver: Brett Porter
Date: Mon, 7 Jun 2004 8:31 AM
needs to be filed in Ant. If it is addressed in a later version, then will have to wait for an Ant upgrade post 1.0.
Will keep in mind for any jar code in m2.
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPJAR-28
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPJAR-28
Summary: Broken Class-Path entry in manifest.mf
Type: Bug
Status: Closed
Priority: Major
Resolution: WON'T FIX
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-jar-plugin
Assignee: Brett Porter
Reporter: Janne Kario
Created: Thu, 3 Jun 2004 9:47 AM
Updated: Mon, 7 Jun 2004 8:31 AM
Environment: Maven RC3, Java 1.4.2_03
Description:
Class-Path manifest entry created by the jar plugin is wrapped at 70 chars resulting in a broken manifest entry.
eg.
Class-Path: *******-common-1.0.jar *******-jms-1.0.jar ***********-ej
b-1.0.jar mx4j-jmx-2.0.1.jar mx4j-2.0.1.jar mx4j-tools-2.0.1.jar mx4j
-impl-2.0.1.jar log4j-1.2.8.jar
Each manifest entry line ends at char number 70. The next line begins with a space.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MPJAR-28) Broken Class-Path entry in manifest.mf
Posted by ji...@codehaus.org.
The following comment has been added to this issue:
Author: Emmanuel Venisse
Created: Thu, 3 Jun 2004 10:05 AM
Body:
It's the jar specification.
http://java.sun.com/j2se/1.3/docs/guide/jar/jar.html
"Line length:
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)."
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MPJAR-28?page=comments#action_20315
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPJAR-28
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPJAR-28
Summary: Broken Class-Path entry in manifest.mf
Type: Bug
Status: Open
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-jar-plugin
Assignee: Jason van Zyl
Reporter: Janne Kario
Created: Thu, 3 Jun 2004 9:47 AM
Updated: Thu, 3 Jun 2004 10:05 AM
Environment: Maven RC3, Java 1.4.2_03
Description:
Class-Path manifest entry created by the jar plugin is wrapped at 70 chars resulting in a broken manifest entry.
eg.
Class-Path: *******-common-1.0.jar *******-jms-1.0.jar ***********-ej
b-1.0.jar mx4j-jmx-2.0.1.jar mx4j-2.0.1.jar mx4j-tools-2.0.1.jar mx4j
-impl-2.0.1.jar log4j-1.2.8.jar
Each manifest entry line ends at char number 70. The next line begins with a space.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org