[ http://jira.codehaus.org/browse/MNG-1050?page=comments#action_83259 ] Kenney Westerhof commented on MNG-1050: ---------------------------------------
If you want 2.*, you should write [2, 3) (or [2.0, 3.0) ); I think this is perfectly legal. If you want the latest version, whatever that is, you could use [0,) Leaving the high-end limit out means unlimited, just as in the math notation, so I say leave it like this. There's a discussion about versioning and a wiki page in the 2.1 design documents where we need to address this. I think version ranges are flexible enough as is to support any scheme or any version range people want. If you were to limit [2.0,) to [2.0,3.0), how would you specify 2.0 or higher, even including 10.0? Also, linux kernels use a different scheme, where 2.x.* is compatible with 2.(x+1).*, where odd-x'es are comparable to 'alpha'. (so 2.5.10 is actually an alpha for 2.6.0). I opt for close won't fix. > [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 > > > 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