Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Duplicate
-
Affects Version/s: 2.1
-
Fix Version/s: 2.2-beta-2
-
Component/s: None
-
Labels:None
-
Environment:XP Pro SP2
-
Number of attachments :
Description
Similar to MRELEASE-134 in maven-release-plugin
<version>[1.1.0,)</version>
This version range can resolve to the latest dev SNAPSHOT. The assembly plugin should ignore SNAPSHOTS as that is not intended by the unbounded high end of the version range.
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 forgetten when version ranges were implemented.
Issue Links
| This issue relates to: | ||||
| MNG-2978 | Assembly plugin does not resolve version ranges correctly |
|
|
|
please stop creating issues in the plugin projects for that. This is most probably a Maven core issue and you should use the MNG project.