[MSHARED-36] Maven Archiver creates incorrect Class-Path entry in Manifest for deployed snapshots

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: maven-archiver-2.4
• Component/s: maven-archiver
• Assignee: John Dennis Casey
• Reporter: Barrie Treloar
• Created: 19/Jul/06 19:53
• Updated: 22/Sep/08 15:09
• Resolved: 22/Sep/08 15:03

Description

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.

Issue Links

• is related to: MDEPLOY-57 <uniqueVersion>false</uniqueVersion> not honored inside <profile>
• relates to: MDEPLOY-57 <uniqueVersion>false</uniqueVersion> not honored inside <profile>
• relates to: MASSEMBLY-67 assembling dependent jars or snapshots uses timestamp formatted version instead of ${version}
• relates to: MJAR-28 Using the jar plugin with addClasspath and snapshots can create manifest classpath with incorrect jar versions