You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Barrie Treloar <ba...@gmail.com> on 2008/10/19 12:32:39 UTC
working around eclipse artifacts in repo version problems: Couldn't find a version in [1.0.0-v20070606] to match range [1.0.0,2.0.0)
How do I work around this type of problem?
--- CONSOLE LOG ---
[INFO] Failed to resolve artifact.
Couldn't find a version in [1.0.0-v20070606] to match range [1.0.0,2.0.0)
org.eclipse.equinox:app:jar:null
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
--- CONSOLE LOG ---
Unfortunately the output doesn't specify which jar caused the
OverConstrainedVersionException.
Can I just hard code the dependency to the value I want once I find the culprit?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: working around eclipse artifacts in repo version problems: Couldn't find a version in [1.0.0-v20070606] to match range [1.0.0,2.0.0)
Posted by Barrie Treloar <ba...@gmail.com>.
On Mon, Oct 20, 2008 at 12:47 AM, Stephen Connolly
<st...@gmail.com> wrote:
> you could change your range to be
>
> [1.0.0-!,2.0.0)
>
> the range you have specified starts with a version without a qualifier.
>
> qualified versions are before versions without a qualifier in Maven version
> ranges...
>
> so 1.0.0-v20070606 < 1.0.0 and therefore outside the range you have
> specified.
>
> The issue with including qualifiers is that now -SNAPSHOT builds can be
> included in the range.
Yeah, its a problem with the Maven <-> Eclipse version transformation.
The version ranges of the org.eclipse.* jars in the maven central repo
are unfortunately defined this way.
> The other option is to exclude all the transitive dependencies and add back
> in the version you want
This is what I have done.
I was wondering if there were alternatives though as this is a painful
process :)
I think I will also look at the code and make changes so that it
informs what in the process caused the over constraining.
At the moment, I can't tell, that information is not available.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: working around eclipse artifacts in repo version problems: Couldn't find a version in [1.0.0-v20070606] to match range [1.0.0,2.0.0)
Posted by Stephen Connolly <st...@gmail.com>.
you could change your range to be
[1.0.0-!,2.0.0)
the range you have specified starts with a version without a qualifier.
qualified versions are before versions without a qualifier in Maven version
ranges...
so 1.0.0-v20070606 < 1.0.0 and therefore outside the range you have
specified.
The issue with including qualifiers is that now -SNAPSHOT builds can be
included in the range.
The other option is to exclude all the transitive dependencies and add back
in the version you want
2008/10/19 Barrie Treloar <ba...@gmail.com>
> How do I work around this type of problem?
>
> --- CONSOLE LOG ---
> [INFO] Failed to resolve artifact.
>
> Couldn't find a version in [1.0.0-v20070606] to match range [1.0.0,2.0.0)
> org.eclipse.equinox:app:jar:null
>
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> --- CONSOLE LOG ---
>
> Unfortunately the output doesn't specify which jar caused the
> OverConstrainedVersionException.
>
> Can I just hard code the dependency to the value I want once I find the
> culprit?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>