t doing this breaks other unit tests.
I'll make an IT test and see what happens just patching the contains
method.
-Original Message-
From: Kenney Westerhof [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 15, 2007 9:18 AM
To: Maven Developers List
Subject: Re: version range quest
st patching the contains
method.
-Original Message-
From: Kenney Westerhof [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 15, 2007 9:18 AM
To: Maven Developers List
Subject: Re: version range question
Brian E. Fox wrote:
> Well, I made the change and all the IT tests pass. I'm not s
do much to solve the real problem.
-Original Message-
From: Kenney Westerhof [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 15, 2007 8:46 AM
To: Maven Developers List
Subject: Re: version range question
Brian E. Fox wrote:
The problem is that I assumed "2.0.5" == "
solve
the real problem.
-Original Message-
From: Kenney Westerhof [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 15, 2007 8:46 AM
To: Maven Developers List
Subject: Re: version range question
Brian E. Fox wrote:
> The problem is that I assumed "2.0.5" == "[2.0.5,)"
VersionSpecificationException
{
VersionRange vr = null;
vr = VersionRange.createFromVersionSpec( requiredVersionRange );
return vr.containsVersion( actualVersion );
}
-Original Message-
From: Kenney Westerhof [mailto:[EMAIL PROTECTED]
Sent:
ception
{
VersionRange vr = null;
vr = VersionRange.createFromVersionSpec( requiredVersionRange );
return vr.containsVersion( actualVersion );
}
-Original Message-
From: Kenney Westerhof [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 15, 2007 5:45 AM
To: Maven Developer
be not if it's not really used) I'd like
someone to bless it.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlos
Sanchez
Sent: Wednesday, March 14, 2007 1:06 AM
To: Maven Developers List
Subject: Re: version range question
I would create a
D] On Behalf Of Carlos
Sanchez
Sent: Wednesday, March 14, 2007 1:06 AM
To: Maven Developers List
Subject: Re: version range question
I would create a jira issue with your tests as unit tests
then search for usages of createFromVersionSpec through the whole
maven and see how it's used
On 3
Maven Developers List
Subject: Re: version range question
I would create a jira issue with your tests as unit tests
then search for usages of createFromVersionSpec through the whole
maven and see how it's used
On 3/13/07, Brian E. Fox <[EMAIL PROTECTED]> wrote:
> I'm still hav
insVersion( actualVersion );
System.out.println( "is "+actualVersion+" contained in
"+requiredVersionRange+" ->" + result );
}
}
-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: Sunday, February 18, 2007 8:15 PM
To: Maven Developer
ateFromVersionSpec( requiredVersionRange );
boolean result = vr.containsVersion( actualVersion );
System.out.println( "is "+actualVersion+" contained in
"+requiredVersionRange+" ->" + result );
}
}
-Original Message-
From: Brian E. Fox [m
:15 PM
To: Maven Developers List
Subject: version range question
According to the javadoc for VersionRange.createFromVersionSpec, a
singular version (ie "2.0.4") is allowed:
/**
* Create a version range from a string representation
*
* Some spec ex
According to the javadoc for VersionRange.createFromVersionSpec, a
singular version (ie "2.0.4") is allowed:
/**
* Create a version range from a string representation
*
* Some spec examples are
*
* 1.0 Version 1.0
* [1.0,2.0) Versions 1.0 (included) to
13 matches
Mail list logo
