You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "David Hoffer (JIRA)" <ji...@codehaus.org> on 2007/05/04 18:10:26 UTC

[jira] Updated: (MNG-2978) Assembly plugin does not resolve version ranges correctly

     [ http://jira.codehaus.org/browse/MNG-2978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Hoffer updated MNG-2978:
------------------------------

    Attachment: VersionRangeSnapshotFix.patch

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.

> Assembly plugin does not resolve version ranges correctly
> ---------------------------------------------------------
>
>                 Key: MNG-2978
>                 URL: http://jira.codehaus.org/browse/MNG-2978
>             Project: Maven 2
>          Issue Type: Bug
>    Affects Versions: 2.0.6
>         Environment: XP Pro SP2
>            Reporter: David Hoffer
>         Attachments: VersionRangeSnapshotFix.patch
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira