[MNG-2978] Assembly plugin does not resolve version ranges correctly

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.0.6
• Environment: XP Pro SP2
• Flags: Patch
• Assignee: Unassigned
• Reporter: David Hoffer
• Created: 03/May/07 20:43
• Updated: 05/Apr/15 22:33
• Resolved: 01/Jun/07 15:50

Description

Similar to MRELEASE-134 in maven-release-plugin

<dependency>
<groupId>myGroup</groupId>
<artifactId>myArtifact</artifactId>
<version>[1.0,)</version>
</dependency>

This version range can resolve to the latest development SNAPSHOT. All artifact dependencies should ignore SNAPSHOTS as that is not intended by the unbounded high end of the version range. This should resolve to any released version of 1.1 or higher.

This document:
http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution#DependencyMediationandConflictResolution-DependencyVersionRanges
addressed the requirements for version ranges and stated that "Resolution of dependency ranges should not resolve to a snapshot (development version) unless it is included as an explicit boundary". I think this requirement was forgotten when version ranges were implemented.

Issue Links

• is duplicated by: MNG-3001 Maven2 does not resolve version ranges correctly [PATCH INCLUDED]
• is related to: MASSEMBLY-208 Assembly plugin does not resolve version ranges correctly
• is related to: MNG-3109 version ranges can include snapshots
• is related to: MNG-2431 Make it possible to specify that version should be the LATEST STABLE available