Maven 2.0.5+ fails to resolve ${project.version} on deployment
--------------------------------------------------------------
Key: MNG-3009
URL: http://jira.codehaus.org/browse/MNG-3009
Project: Maven 2
Issue Type: Bug
Components: Deployment
Affects Versions: 2.0.6, 2.0.5
Reporter: Stefan Behnel
Priority: Blocker
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.
--
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
