You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by ji...@codehaus.org on 2004/06/26 10:15:34 UTC
[jira] Created: (MAVEN-1340) Dependency version flexibility
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MAVEN-1340
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-1340
Summary: Dependency version flexibility
Type: Improvement
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
model
Versions:
1.0-rc3
Assignee:
Reporter: Andy Jefferson
Created: Sat, 26 Jun 2004 4:12 AM
Updated: Sat, 26 Jun 2004 4:12 AM
Environment: 1.0-rc3
Description:
I searched and couldn't find any mention of this as such. Please delete if already registered.
In a dependency I currently specify the version XML tag. The version has to be an actual version, or SNAPSHOT. How about allowing users to specify "min 'version'". So for example, in my system I require the user having log4j at least 1.2.0. So I would really like to say
<version>min 1.2.0</version>
and then if it finds 1.2.3 on their system it accepts that. Currently I have to specify a specific version, which can force them to download it. This would allow much more flexibility. Clearly you would have to make some assumptions on the naming scheme for version, but there are established conventions for that that the majority of projects adopt. Alternatives to the "min 'version'" could be to specify a comma separated version list
<version>1.2.0, 1.2.1, 1.2.7</version>
this second one may be easier to implement since its just a matter of checking against the list of options.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report 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] Closed: (MAVEN-1340) Dependency version flexibility
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MAVEN-1340?page=all ]
Brett Porter closed MAVEN-1340:
-------------------------------
Resolution: Won't Fix
will be dealt with in Maven 2.0 (dependency mediation features). Maven 1.1 is unlikely to be capable of it given the architecture required to support it.
> Dependency version flexibility
> ------------------------------
>
> Key: MAVEN-1340
> URL: http://jira.codehaus.org/browse/MAVEN-1340
> Project: maven
> Type: Improvement
> Components: model
> Versions: 1.0-rc3
> Environment: 1.0-rc3
> Reporter: Andy Jefferson
>
>
> I searched and couldn't find any mention of this as such. Please delete if already registered.
> In a dependency I currently specify the version XML tag. The version has to be an actual version, or SNAPSHOT. How about allowing users to specify "min 'version'". So for example, in my system I require the user having log4j at least 1.2.0. So I would really like to say
> <version>min 1.2.0</version>
> and then if it finds 1.2.3 on their system it accepts that. Currently I have to specify a specific version, which can force them to download it. This would allow much more flexibility. Clearly you would have to make some assumptions on the naming scheme for version, but there are established conventions for that that the majority of projects adopt. Alternatives to the "min 'version'" could be to specify a comma separated version list
> <version>1.2.0, 1.2.1, 1.2.7</version>
> this second one may be easier to implement since its just a matter of checking against the list of options.
--
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: (MAVEN-1340) Dependency version flexibility
Posted by ji...@codehaus.org.
The following comment has been added to this issue:
Author: Carlos Sanchez
Created: Sat, 26 Jun 2004 6:43 AM
Body:
Specifying a min version can cause problems as there are versions not compatible, for example a library 3.0 may be not compatible with 2.0
A solution could be add a <version> tag for each allowed version.
<version>1.2</version>
<version>1.2.1</version>
<version>1.2.2</version>
And do an OR of them
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MAVEN-1340?page=comments#action_21057
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MAVEN-1340
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-1340
Summary: Dependency version flexibility
Type: Improvement
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
model
Versions:
1.0-rc3
Assignee:
Reporter: Andy Jefferson
Created: Sat, 26 Jun 2004 4:12 AM
Updated: Sat, 26 Jun 2004 6:43 AM
Environment: 1.0-rc3
Description:
I searched and couldn't find any mention of this as such. Please delete if already registered.
In a dependency I currently specify the version XML tag. The version has to be an actual version, or SNAPSHOT. How about allowing users to specify "min 'version'". So for example, in my system I require the user having log4j at least 1.2.0. So I would really like to say
<version>min 1.2.0</version>
and then if it finds 1.2.3 on their system it accepts that. Currently I have to specify a specific version, which can force them to download it. This would allow much more flexibility. Clearly you would have to make some assumptions on the naming scheme for version, but there are established conventions for that that the majority of projects adopt. Alternatives to the "min 'version'" could be to specify a comma separated version list
<version>1.2.0, 1.2.1, 1.2.7</version>
this second one may be easier to implement since its just a matter of checking against the list of options.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report 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