[
http://jira.codehaus.org/browse/MNG-2486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kenney Westerhof updated MNG-2486:
----------------------------------
Assignee: (was: Kenney Westerhof)
Affects Version/s: 2.1-alpha-1
2.0.7
2.0.5
2.0.6
Fix Version/s: (was: Reviewed Pending Version Assignment)
2.1-alpha-1
2.0.8
Issue Type: Bug (was: Improvement)
Summary: ${project.version} evaluated to timestamped version if
referring to SNAPSHOT (was: disallow use of ${project.version} in dependency
versions)
> ${project.version} evaluated to timestamped version if referring to SNAPSHOT
> ----------------------------------------------------------------------------
>
> Key: MNG-2486
> URL: http://jira.codehaus.org/browse/MNG-2486
> Project: Maven 2
> Issue Type: Bug
> Components: Dependencies, Inheritance and Interpolation, POM
> Affects Versions: 2.0.4, 2.0.5, 2.0.6, 2.0.7, 2.1-alpha-1
> Reporter: John Casey
> Priority: Critical
> Fix For: 2.0.8, 2.1-alpha-1
>
>
> when projects specify dependencyManagement sections with a shorthand version
> notation using the current project version (using ${project.version}) the
> version resolved will be that of the POM in which the dependencyManagement
> section is specified. If this POM is a snapshot, these dependency
> specifications will get the timestamp/buildnumber of that POM, instead of the
> actual one used when the dependency it references gets deployed.
> We should look at strategies for limiting or eliminating this practice, or
> else (somehow) pulling the real timestamp/buildnumber for that artifact from
> the reactor...in order to make these deps transitively resolvable for users.
--
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
