You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2010/03/18 14:24:23 UTC

[jira] Closed: (MNG-2486) ${project.version} evaluated to timestamped version if referring to SNAPSHOT

     [ http://jira.codehaus.org/browse/MNG-2486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Bentmann closed MNG-2486.
----------------------------------

    Resolution: Fixed
      Assignee: Benjamin Bentmann

This is already fixed in 2.0.5. The reason this might have shown up with later versions as well is that the actual issue is caused by badly deployed POMs, which would make newer Maven versions fail as well.

> ${project.version} evaluated to timestamped version if referring to SNAPSHOT
> ----------------------------------------------------------------------------
>
>                 Key: MNG-2486
>                 URL: http://jira.codehaus.org/browse/MNG-2486
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Dependencies, Inheritance and Interpolation, POM
>    Affects Versions: 2.0.4, 2.0.5, 2.0.6, 2.0.7, 3.0-alpha-1
>            Reporter: John Casey
>            Assignee: Benjamin Bentmann
>            Priority: Critical
>             Fix For: 2.0.5
>
>
> 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