You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Andrew Williams (JIRA)" <ji...@codehaus.org> on 2007/03/12 18:53:35 UTC
[jira] Closed: (MNG-1050) [2.0,) should not select 3.0 and above by
default
[ http://jira.codehaus.org/browse/MNG-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Williams closed MNG-1050.
--------------------------------
Resolution: Won't Fix
Agreed, this is the correct behaviour. Maven cannot assume that versions are incompatible, it uses flexible versions by default on purpose.
The client is free to restrict the versions as Kenney stated if they do not wish to update to the latest version.
If the maven versioning ranges are not operating correcty that is a seperate point.
> [2.0,) should not select 3.0 and above by default
> -------------------------------------------------
>
> Key: MNG-1050
> URL: http://jira.codehaus.org/browse/MNG-1050
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
> Reporter: Brett Porter
> Fix For: 2.1.x
>
>
> I think that we need to assume major versions are incompatible as it is easier to later state compatibility than fix it when broken.
> This might just be a default compatibility scheme, but a project can define its own (eg, compatible-since 2.1).
--
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