You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Phillip Hellewell <ss...@gmail.com> on 2010/12/10 06:00:21 UTC
Can't resolve dependency with version range
I'm using Maven 2.2.1. It won't resolve a dependency with a locked
down version like [1.0.0.6] if the metadata xml file in the local repo
does not have that version. It won't look in my remote repo, which
does have the version I need. But if I delete the metadata xml
file(s) in my local repo, then it works.
I searched the mail archives and found a lot of topics similar to
this, but I couldn't find a clear enough explanation to understand
whether I'm doing something wrong or if this is just a bug.
Phillip
P.S. Here's an example output of the error.
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
Couldn't find a version in [1.0.0.4, 1.0.0.5] to match range [1.0.0.6,1.0.0.6]
ad.core:cppunitlite:zip:null
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
adrepo-public (http://maven.example.com:8080/nexus/content/groups/public)
Path to dependency:
1) ad.core:core:pom:1.0.0.46-SNAPSHOT
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Can't resolve dependency with version range
Posted by Anders Hammar <an...@hammar.net>.
Oh, yes. I don't recommend using anything but Maven 3.0.
/Anders
On Sat, Dec 11, 2010 at 00:38, Phillip Hellewell <ss...@gmail.com> wrote:
> On Fri, Dec 10, 2010 at 2:45 PM, Anders Hammar <an...@hammar.net> wrote:
> > Maven 3.0 rocks! :-)
>
> Would you recommend it in a production environment?
>
> Phillip
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Can't resolve dependency with version range
Posted by Phillip Hellewell <ss...@gmail.com>.
On Fri, Dec 10, 2010 at 2:45 PM, Anders Hammar <an...@hammar.net> wrote:
> Maven 3.0 rocks! :-)
Would you recommend it in a production environment?
Phillip
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Is Maven able to count the number of skipped unit tests?
Posted by Stefan Egeler <St...@loyaltypartner.com>.
Hello,
We are setting up a quality dashboard for administrate our metrics. For this, we need to know if Maven is able to count (and transmit) the number of skipped unit tests. Is it able to do this?
Stefan Egeler
The information in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee and access to the e-mail by anyone else is prohibited. If you are not the intended recipient, any disclosure, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Common e-mails are not protected against access by third persons and therefore might be lost, changed or falsified, with or without any interference by third persons. We cannot accept any responsibility for the integrity of e-mails or for any damages resulting out of these circumstances.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Can't resolve dependency with version range
Posted by Anders Hammar <an...@hammar.net>.
Maven 3.0 rocks! :-)
/Anders
On Fri, Dec 10, 2010 at 22:36, Phillip Hellewell <ss...@gmail.com> wrote:
> On Fri, Dec 10, 2010 at 10:16 AM, Phillip Hellewell <ss...@gmail.com>
> wrote:
> > I tried starting from scratch with similar steps that I was using to
> > reproduce it yesterday, and now I can't reproduce it anymore.
> >
> > But if I do reproduce it again, I'll try the -U option to see if it helps
> :)
>
> I ran into it again, and adding -U sure enough worked.
>
> I don't understand why I should need -U though. I mean, if it can't
> find it in the local repo, of course it ought to look in remote repos,
> and most the time it does. Oh well, whatever is going on appears to
> be fixed in Maven 3.x, so I won't worry about it too much.
>
> Phillip
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Can't resolve dependency with version range
Posted by Phillip Hellewell <ss...@gmail.com>.
On Fri, Dec 10, 2010 at 10:16 AM, Phillip Hellewell <ss...@gmail.com> wrote:
> I tried starting from scratch with similar steps that I was using to
> reproduce it yesterday, and now I can't reproduce it anymore.
>
> But if I do reproduce it again, I'll try the -U option to see if it helps :)
I ran into it again, and adding -U sure enough worked.
I don't understand why I should need -U though. I mean, if it can't
find it in the local repo, of course it ought to look in remote repos,
and most the time it does. Oh well, whatever is going on appears to
be fixed in Maven 3.x, so I won't worry about it too much.
Phillip
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Can't resolve dependency with version range
Posted by Phillip Hellewell <ss...@gmail.com>.
I tried starting from scratch with similar steps that I was using to
reproduce it yesterday, and now I can't reproduce it anymore.
But if I do reproduce it again, I'll try the -U option to see if it helps :)
Phillip
On Fri, Dec 10, 2010 at 10:11 AM, Phillip Hellewell <ss...@gmail.com> wrote:
> On Thu, Dec 9, 2010 at 11:37 PM, Anders Hammar <an...@hammar.net> wrote:
>> Did you try forcing an update ("-U") with Maven 2? I don't know if that
>> should have worked, but I would have tried it...
>
> Interestingly, today it is working, even without a -U or anything.
>
> I wonder if there is some kind of time frame where Maven 2.x won't
> look at remote repo until a certain time has passed. I could
> understand that kind of behavior for snapshots, but I don't understand
> doing it for version ranges.
>
> Phillip
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Can't resolve dependency with version range
Posted by Phillip Hellewell <ss...@gmail.com>.
On Thu, Dec 9, 2010 at 11:37 PM, Anders Hammar <an...@hammar.net> wrote:
> Did you try forcing an update ("-U") with Maven 2? I don't know if that
> should have worked, but I would have tried it...
Interestingly, today it is working, even without a -U or anything.
I wonder if there is some kind of time frame where Maven 2.x won't
look at remote repo until a certain time has passed. I could
understand that kind of behavior for snapshots, but I don't understand
doing it for version ranges.
Phillip
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Can't resolve dependency with version range
Posted by Anders Hammar <an...@hammar.net>.
Did you try forcing an update ("-U") with Maven 2? I don't know if that
should have worked, but I would have tried it...
/Anders
On Fri, Dec 10, 2010 at 06:19, Phillip Hellewell <ss...@gmail.com> wrote:
> Ok, some good news. I just did the same test with Maven 3.0.1 and it
> worked no problem. It downloaded the new version from the remote repo
> like it was supposed to.
>
> But I don't know if I'm ready to migrate to Maven 3.x yet...
>
> Phillip
>
> On Thu, Dec 9, 2010 at 10:00 PM, Phillip Hellewell <ss...@gmail.com>
> wrote:
> > I'm using Maven 2.2.1. It won't resolve a dependency with a locked
> > down version like [1.0.0.6] if the metadata xml file in the local repo
> > does not have that version. It won't look in my remote repo, which
> > does have the version I need. But if I delete the metadata xml
> > file(s) in my local repo, then it works.
> >
> > I searched the mail archives and found a lot of topics similar to
> > this, but I couldn't find a clear enough explanation to understand
> > whether I'm doing something wrong or if this is just a bug.
> >
> > Phillip
> >
> > P.S. Here's an example output of the error.
> >
> > [ERROR] BUILD ERROR
> > [INFO]
> ------------------------------------------------------------------------
> > [INFO] Failed to resolve artifact.
> >
> > Couldn't find a version in [1.0.0.4, 1.0.0.5] to match range
> [1.0.0.6,1.0.0.6]
> > ad.core:cppunitlite:zip:null
> >
> > from the specified remote repositories:
> > central (http://repo1.maven.org/maven2),
> > adrepo-public (
> http://maven.example.com:8080/nexus/content/groups/public)
> >
> > Path to dependency:
> > 1) ad.core:core:pom:1.0.0.46-SNAPSHOT
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Can't resolve dependency with version range
Posted by Phillip Hellewell <ss...@gmail.com>.
Ok, some good news. I just did the same test with Maven 3.0.1 and it
worked no problem. It downloaded the new version from the remote repo
like it was supposed to.
But I don't know if I'm ready to migrate to Maven 3.x yet...
Phillip
On Thu, Dec 9, 2010 at 10:00 PM, Phillip Hellewell <ss...@gmail.com> wrote:
> I'm using Maven 2.2.1. It won't resolve a dependency with a locked
> down version like [1.0.0.6] if the metadata xml file in the local repo
> does not have that version. It won't look in my remote repo, which
> does have the version I need. But if I delete the metadata xml
> file(s) in my local repo, then it works.
>
> I searched the mail archives and found a lot of topics similar to
> this, but I couldn't find a clear enough explanation to understand
> whether I'm doing something wrong or if this is just a bug.
>
> Phillip
>
> P.S. Here's an example output of the error.
>
> [ERROR] BUILD ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
>
> Couldn't find a version in [1.0.0.4, 1.0.0.5] to match range [1.0.0.6,1.0.0.6]
> ad.core:cppunitlite:zip:null
>
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2),
> adrepo-public (http://maven.example.com:8080/nexus/content/groups/public)
>
> Path to dependency:
> 1) ad.core:core:pom:1.0.0.46-SNAPSHOT
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org