El 27/06/2006 18:55, Mike Perham escribió:
Akbarr, you might want to watch this issue.
http://jira.codehaus.org/browse/MRELEASE-134
Voted
[Akbarr]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-ma
Jörg Schaible <[EMAIL PROTECTED]> writes:
>
>
> You have to add the artifact as first class dependency in your POM
> (without a version field).
OK, seems to work that way. Thanks a lot for the quick answer.
--
OQube < software engineering \ génie logiciel >
Arnaud Bailly, Dr.
\web> http://www.
Hi Arnaud,
Arnaud Bailly wrote on Wednesday, June 28, 2006 8:58 AM:
[snip]
> Hello,
> I also have troubles with dependencies range:
> In my parent pom, I put :
>
>
>
>
> commons-collections
> commons-collections
> (,3.0)
>
>
>
>
> but mvn -X gives me:
>
[snip]
Akbarr <[EMAIL PROTECTED]> writes:
> But I'm not sure whether it's an implemented feature or not. I have a POM
> with a dependency:
>
>
> com.digibis
> digisqlhib
> [1.3, ]
>
>
>
>
>
Hello,
I also have troubles with dependencies range:
In my parent pom, I put :
commons-c
Akbarr, you might want to watch this issue.
http://jira.codehaus.org/browse/MRELEASE-134
-Original Message-
From: Akbarr [mailto:[EMAIL PROTECTED]
Sent: Thu 6/22/2006 12:22 PM
To: Maven Users List
Subject: M2: Using version ranges in dependencies
Hi all,
I have a doubt with dependenci
On 6/23/06, Mike Perham <[EMAIL PROTECTED]> wrote:
Yep, I just ran into this also. I have a module which has [1.1.0,) and
1.1.0 and 1.1.1-SNAPSHOT in my local repo. I can't release the module.
It basically makes dependency ranges unusable for us. I'm unclear who's
at fault here (the release p
Yep, I just ran into this also. I have a module which has [1.1.0,) and
1.1.0 and 1.1.1-SNAPSHOT in my local repo. I can't release the module.
It basically makes dependency ranges unusable for us. I'm unclear who's
at fault here (the release plugin, maven's dependency resolution
alogrithm, etc) b
