You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2005/09/30 17:23:11 UTC
[jira] Created: (MNG-1050) [2.0,) should not select 3.0 and above by default
[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
Type: Bug
Components: maven-artifact
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MNG-1050) [2.0,) should not select 3.0 and above by default
Posted by "Joerg Schaible (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1050?page=comments#action_50879 ]
Joerg Schaible commented on MNG-1050:
-------------------------------------
IMHO "[2.0,)" is perfect for any new version. It depends on the version naming policy of the depending artifact's project, if a new release is compatible. E.g. a lot of Jakarta common jars are not even compatible for minor version upgrades, while e.g. CGLIB 2.x is backward compatible to 1.x. Additionally it depends on the current artifact's usega of the dependency. If only API is used that is part of the official API (e.g. avalon-framework-api) or also classes that are supposed to be internal (avalon-framework-impl). So the author of an artifact may define the compatible version range for a dependency depending on the usage e.g. "[2.0,3.0)" if he really cares. A "compatible-since" would help tremendously though ;-)
Also it should be possible to make a hint, if the (major?) versions of a library can coexist, e.g. webwork 1.x and webwork 2.x. This is interesting for library authors, that want to support both versions in their project (as e.g. nanocontainer-nanowar does for webwork). ASM 1.x and 2.x is an example, where this is not possible.
> [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
> Type: Bug
> Components: maven-artifact
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org