[MASSEMBLY-67] assembling dependent jars or snapshots uses timestamp formatted version instead of ${version}

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.2-beta-1
• Assignee: John Dennis Casey
• Reporter: Mark J. Titorenko
• Created: 08/Feb/06 07:44
• Updated: 06/Apr/15 01:16
• Resolved: 11/Aug/06 10:31

Description

I'm using the jar plugin to add my dependencies to the manifest. I'm also using the assembly plugin to package all dependencies into one archive. The problem is that the jar manifest adds my dependencies as "foo-SNAPHOT" and the archiver adds them as "foo-20041113.jar".

This causes my snapshot classes to not be found at runtime.

Issue Links

• is duplicated by: MASSEMBLY-91 Currently the assembly plugin renames SNAPSHOT dependencies to a date stamp ex. api-authorisation-4.00-20060502.150651-20.jar
• is related to: MJAR-28 Using the jar plugin with addClasspath and snapshots can create manifest classpath with incorrect jar versions
• is related to: MSHARED-36 Maven Archiver creates incorrect Class-Path entry in Manifest for deployed snapshots
• relates to: MASSEMBLY-3 assembling dependencies uses timestamp instead of snapshot jars