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/02 15:39:26 UTC
[jira] Created: (MDEP-88) Dependency plugin does not resolve
version ranges correctly
Dependency plugin does not resolve version ranges correctly
-----------------------------------------------------------
Key: MDEP-88
URL: http://jira.codehaus.org/browse/MDEP-88
Project: Maven 2.x Dependency Plugin
Issue Type: Bug
Affects Versions: 2.0-alpha-4
Environment: XP Pro SP2
Reporter: David Hoffer
Assignee: Brian Fox
Similar to MRELEASE-134 in maven-release-plugin
<version>[1.1.0,)</version>
This version range can resolve to the latest dev SNAPSHOT. The dependency 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.
--
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
[jira] Closed: (MDEP-88) Dependency plugin does not resolve version
ranges correctly
Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEP-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Fox closed MDEP-88.
-------------------------
Resolution: Won't Fix
MDEP-50 has been added to support ranges in the unpack goal. unpack-dependencies uses core functionality to resolve the ranges and thus the behavior can't be fixed in the plugin.
> Dependency plugin does not resolve version ranges correctly
> -----------------------------------------------------------
>
> Key: MDEP-88
> URL: http://jira.codehaus.org/browse/MDEP-88
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Affects Versions: 2.0-alpha-4
> Environment: XP Pro SP2
> Reporter: David Hoffer
> Assignee: Brian Fox
>
> Similar to MRELEASE-134 in maven-release-plugin
> <version>[1.1.0,)</version>
> This version range can resolve to the latest dev SNAPSHOT. The dependency 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.
--
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