maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Fox (JIRA)" <>
Subject [jira] Commented: (MNG-2486) ${project.version} evaluated to timestamped version if referring to SNAPSHOT
Date Wed, 30 Dec 2009 19:57:55 GMT


Brian Fox commented on MNG-2486:

I'm pretty sure this is already fixed even in 2.x.

> ${project.version} evaluated to timestamped version if referring to SNAPSHOT
> ----------------------------------------------------------------------------
>                 Key: MNG-2486
>                 URL:
>             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
>            Priority: Critical
>             Fix For: 3.0-alpha-7
> 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 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:
For more information on JIRA, see:


View raw message