The following issue has been updated:
Updater: Dennis Lundberg (mailto:[EMAIL PROTECTED])
Date: Sat, 7 Aug 2004 6:53 PM
Comment:
This patch fixes this issue. It also fixes several minor errors in the documentation.
Changes:
Attachment changed to MPJAR-35.patch
---------------------------------------------------------------------
For a full history of the issue, see:
http://jira.codehaus.org/browse/MPJAR-35?page=history
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPJAR-35
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPJAR-35
Summary: Documentation does not mention need for jar.manifest.classpath property
Type: Bug
Status: Open
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-jar-plugin
Versions:
1.6
Assignee: Jason van Zyl
Reporter: Erik Husby
Created: Wed, 4 Aug 2004 10:59 AM
Updated: Sat, 7 Aug 2004 6:53 PM
Description:
The properties documentation indicates that setting the
maven.jar.manifest.classpath.add property to true will add a Classpath: entry to the
manifest. What is not mentioned is that the jars need to be tagged with the property
<jar.manifest.classpath>true</jar.manifest.classpath> in the project.xml.
---------------------------------------------------------------------
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
