version ranges can include snapshots

Details

Type: Bug

Status:Closed

Priority: Major

Resolution:
Duplicate

Affects Version/s:2.0.4, 2.0.5, 2.0.6, 2.0.7

Fix Version/s:
None

Component/s:
None

Labels:

None

Description

<version>[1.1.0,)</version>

This version range can resolve to the latest dev SNAPSHOT which causes the release plugin to fail due to a SNAPSHOT dependency. The release plugin should check that the original version specification includes a non-SNAPSHOT version (1.1.0) and so can be released without harm.

Issue Links

duplicates

MNG-3092Resolution of version ranges with non-snapshot bounds can resolve to a snapshot version

Akbarr
added a comment - 28/Jun/06 10:29 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.

Does anyone know when this will be resolved? Also, it seems that all (most) other plug-ins have the same problem; I have observed this bug with the idea, assembly & dependency plug-in. It seems troubling to me that so many plug-ins have this bug.

What are the workarounds for this? We are to the point of being forced to not use version ranges, but we don't want to do this because the practice works so well if it were not for the bug!

What are the options?

If you don't use version ranges, how can you get the same behavior?

Could this be fixed? Where is the code that resolves version ranges? Is this shared across all plug-in or does each implement this in their own way?

David Hoffer
added a comment - 30/Apr/07 15:32 Does anyone know when this will be resolved? Also, it seems that all (most) other plug-ins have the same problem; I have observed this bug with the idea, assembly & dependency plug-in. It seems troubling to me that so many plug-ins have this bug.
What are the workarounds for this? We are to the point of being forced to not use version ranges, but we don't want to do this because the practice works so well if it were not for the bug!
What are the options?
If you don't use version ranges, how can you get the same behavior?
Could this be fixed? Where is the code that resolves version ranges? Is this shared across all plug-in or does each implement this in their own way?