Maven 2 & 3

Assembly plugin does not resolve version ranges correctly

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Duplicate
  • Affects Version/s: 2.0.6
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None
  • Environment:
    XP Pro SP2
  • Complexity:
    Intermediate
  • Patch Submitted:
    Yes
  • Number of attachments :
    1

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

Bug - A problem which impairs or prevents the functions of the product. MNG-3001 Maven2 does not resolve version ranges correctly [PATCH INCLUDED]

  • Blocker - Blocks development and/or testing work, production could not run
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
is related to

Bug - A problem which impairs or prevents the functions of the product. MASSEMBLY-208 Assembly plugin does not resolve version ranges correctly

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Bug - A problem which impairs or prevents the functions of the product. MNG-3109 version ranges can include snapshots

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Improvement - An improvement or enhancement to an existing feature or task. MNG-2431 Make it possible to specify that version should be the LATEST STABLE available

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
David Hoffer added a comment -

Oops, the title should have been "Maven plugin(s) do not resolve version ranges correctly."

The assembly plug-in is one, others are idea and dependency, ... I believe the release plug-in trunk has it fixed but none of its releases do.

Show
David Hoffer added a comment - Oops, the title should have been "Maven plugin(s) do not resolve version ranges correctly." The assembly plug-in is one, others are idea and dependency, ... I believe the release plug-in trunk has it fixed but none of its releases do.
Hide
Permalink
David Hoffer added a comment -

I have included a patch for this bug. The fix is in the containsVersion method of VersionRange. I have added tests in VersionRangeTest and DefaultArtifactCollectorTest. All tests in maven pass with this fix.

Show
David Hoffer added a comment - I have included a patch for this bug. The fix is in the containsVersion method of VersionRange. I have added tests in VersionRangeTest and DefaultArtifactCollectorTest. All tests in maven pass with this fix.

People

  • Assignee:
    Unassigned
    Reporter:
    David Hoffer
Vote (0)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved: