Maven Archiver creates incorrect Class-Path entry in Manifest for deployed
snapshots
------------------------------------------------------------------------------------
Key: MNG-2456
URL: http://jira.codehaus.org/browse/MNG-2456
Project: Maven 2
Issue Type: Bug
Components: maven-archiver
Affects Versions: 2.0.4
Reporter: Baerrach bonDierne
See related problems MJAR-28 and MASSEMBLY-67.
Summary:
The Maven-Archiver uses the file part of the artifact's filename to create the
Class-Path entries in the Manifest.
This works fine for released artifacts and non-deployed snapshot.
The problem occurs when using a deployed snapshot as the assembly plugin will
copy the dependency as ${artifactId}-${version}-timestampedversion.jar and the
entry in the Class-Path will be ${artifactId}-${version}-SNAPSHOT
thus use of java -jar <jarfile> will fail because of the differing names.
--
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