You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@codehaus.org> on 2014/11/25 21:32:10 UTC

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

     [ https://jira.codehaus.org/browse/MIDEA-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov closed MIDEA-90.
-------------------------------

    Resolution: Won't Fix

Please refer to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014 if you're wondering why this issue was closed out.

> IDEA Plugin does not resolve version ranges correctly
> -----------------------------------------------------
>
>                 Key: MIDEA-90
>                 URL: https://jira.codehaus.org/browse/MIDEA-90
>             Project: Maven IDEA Plugin (RETIRED)
>          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 was sent by Atlassian JIRA
(v6.1.6#6162)