[MNG-2486] ${project.version} evaluated to timestamped version if referring to SNAPSHOT

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.0.4, 2.0.5, 2.0.6, 2.0.7, 3.0-alpha-1
• Fix Version/s: 2.0.5
• Component/s: Dependencies, Inheritance and Interpolation, POM
• Assignee: Benjamin Bentmann
• Reporter: John Dennis Casey
• Created: 04/Aug/06 13:31
• Updated: 06/Apr/15 01:36
• Resolved: 18/Mar/10 08:23

Description

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.

Issue Links

• is depended upon by: SUREFIRE-218 Unable to use 2.3-SNAPSHOT
• is duplicated by: MNG-2647 Version not inherited for SNAPSHOT version
• is duplicated by: MNG-2796 Yet another snapshot/timestamp version resolution problem