[MNG-3009] Maven 2.0.5+ fails to resolve ${project.version} on deployment

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Duplicate
• Affects Version/s: 2.0.5, 2.0.6
• Component/s: Deployment
• Assignee: Unassigned
• Reporter: Stefan Behnel
• Created: 24/May/07 05:16
• Updated: 17/Dec/08 22:06
• Resolved: 16/Jun/07 04:55

Description

Starting with version 2.0.5, Maven fails to resolve the ${project.version} variable in poms on (SNAPSHOT?) deployment. This results in corrupted repositories, as Maven will (sporadically) fail to resolve transitive dependencies that involve these references.

The symptom is that Maven will start searching for a magical version "2.4.1" of an artifact, although such a version never existed and was never written in any POM. Dependent builds therefor fail as this version cannot be resolved.

The deploy plugin should always resolve all involved versions when it uploads POMs.

Issue Links

• duplicates: MNG-2339 ${project.*} are interpreted in the wrong place