[ http://jira.codehaus.org/browse/MNG-2486?page=comments#action_71725 ] Brett Porter commented on MNG-2486: -----------------------------------
is this a duplicate of MNG-2339? > disallow use of ${project.version} in dependency versions > --------------------------------------------------------- > > Key: MNG-2486 > URL: http://jira.codehaus.org/browse/MNG-2486 > Project: Maven 2 > Issue Type: Improvement > Components: POM, Inheritence and Interpolation, Dependencies > Affects Versions: 2.0.4 > Reporter: John Casey > Priority: Critical > > 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