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/08/16 19:09:47 UTC

[jira] Commented: (MIDEA-90) IDEA Plugin does not resolve version ranges correctly

    [ http://jira.codehaus.org/browse/MIDEA-90?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105048 ] 

David Hoffer commented on MIDEA-90:
-----------------------------------

Since this issue is related to MNG-3092 you might want to watch/vote for it.

> IDEA Plugin does not resolve version ranges correctly
> -----------------------------------------------------
>
>                 Key: MIDEA-90
>                 URL: http://jira.codehaus.org/browse/MIDEA-90
>             Project: Maven 2.x IDEA Plugin
>          Issue Type: Bug
>    Affects Versions: 2.0, 2.1
>         Environment: Xp Pro SP2
>            Reporter: David Hoffer
>
> Similar to MRELEASE-134 in maven-release-plugin
> <version>[1.1.0,)</version>
> This version range can resolve to the latest dev SNAPSHOT.  The idea 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