Loading...

users@maven.apache.org

[Prev] Thread [Next]  |  [Prev] Date [Next]

Re: OverConstrainedVersionException Stuart McCulloch Tue Jan 29 00:02:59 2008

On 12/12/2007, Saxena, Sandeep <[EMAIL PROTECTED]> wrote:
>
>  When I do a "mvn -e -X clean install" with <version>3.3.0-v3346</version>
>  I get the following traces :
>
>
> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> [DEBUG] Trace
>
> org.apache.maven.lifecycle.LifecycleExecutionException: Couldn't find a
> version in [3.1.1, 3.2.0, 3.3.0-v3346, 3.2.1-v32
>
> 35e] to match range [3.3.0,4.0.0)
>

hmm, this suggests you still have the version with square brackets set
somewhere in your project poms

  org.eclipse:swt:jar:null
>
>
>
> from the specified remote repositories:
>
>   central (http://repo1.maven.org/maven2),
>
>   Maven Central (http://repo1.maven.org),
>
>   Maven Central2 Repository2 (http://repo2.maven.org),
>
>
>
>         at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
> DefaultLifecycleExecutor.java:556)
>
>         at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
> (DefaultLifecycleExecutor.java:48
>
> 0)
>
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal
> (DefaultLifecycleExecutor.java:459)
>
>         at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
> (DefaultLifecycleExecutor.jav
>
> a:311)
>
>         at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
> DefaultLifecycleExecutor.java:278)
>
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
> DefaultLifecycleExecutor.java:143)
>
>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
>
>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
>
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
>
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
>         at sun.reflect.NativeMethodAccessorImpl.invoke(
> NativeMethodAccessorImpl.java:39)
>
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:25)
>
>         at java.lang.reflect.Method.invoke(Method.java:585)
>
>         at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java
> :315)
>
>         at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>
>         at org.codehaus.classworlds.Launcher.mainWithExitCode(
> Launcher.java:430)
>
>         at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>
> Caused by:
> org.apache.maven.artifact.versioning.OverConstrainedVersionException:
> Couldn't find a version in [3.1.1, 3.2.
>
> 0, 3.3.0-v3346, 3.2.1-v3235e] to match range [3.3.0,4.0.0)
>
>   org.eclipse:swt:jar:null
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
>
> Sandeep.
>  ------------------------------
>
> *From:* Stuart McCulloch [mailto:[EMAIL PROTECTED]
> *Sent:* Wednesday, December 12, 2007 12:31 PM
> *To:* Saxena, Sandeep
> *Cc:* Maven Users List
> *Subject:* Re: OverConstrainedVersionException
>
>
>
> On 12/12/2007, *Saxena, Sandeep* <[EMAIL PROTECTED]> wrote:
>
> It gives the same error even if I use    <version>3.3.0-v3346</version>.
>
>
> hmm... well over here it works:
>
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> Downloading:
> http://repo1.maven.org/maven2/org/eclipse/swt/3.3.0-v3346/swt-3.3.0-v3346.pom
> 404b downloaded
> Downloading:
> http://repo1.maven.org/maven2/org/eclipse/swt/3.3.0-v3346/swt-3.3.0-v3346.jar
> 14K downloaded
>
> make sure you've done an "mvn install" on the POM with the dependency
> if it's different to the one that you're building from - also check you
> haven't
> got this version in another POM
>
>
> if it's still failing you can use "mvn -X install" to find out where the
> bad version
> comes from...
>
> BTW what the meaning of <version>[3.3.0-v3346]</version>.
> I thought it is to stop maven looking from higher or lower versions.
>
>
> using just 3.3.0-v3346 should do the same and avoid the versioning
> exception
> - the version range code is probably tripping up over the '-' in the given
> version
>
>
>
> Regards,
> Sandeep.
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Stuart
> McCulloch
> Sent: Wednesday, December 12, 2007 12:15 PM
> To: Maven Users List
> Subject: Re: OverConstrainedVersionException
>
> On 12/12/2007, Saxena, Sandeep <[EMAIL PROTECTED]> wrote:
> >
> > Hi All,
> >
> > I am using following dependency in one of my POMs:
> >
> > +++++++++++++++++++++++++++++++++++
> > <dependency>
> >        <groupId>org.eclipse</groupId>
> >        <artifactId>swt</artifactId>
> >        <version>[ 3.3.0-v3346]</version>
> > </dependency>
> > +++++++++++++++++++++++++++++++++++
> >
> > And getting the following exceptions:
> >
> > ++++++++++++++++++++++++++++++++++++
> > Caused by:
> > org.apache.maven.artifact.versioning.OverConstrainedVersionException:
> > Couldn't find a version in [3.1.1, 3.2.
> > 0, 3.3.0-v3346, 3.2.1-v3235e] to match range [3.3.0, 4.0.0)
> >   org.eclipse: swt: jar: null
> > ++++++++++++++++++++++++++++++++++++
> >
> >
> > Any clues on this and how can it be resolved?
>
>
> why not just use
>
>    <version>3.3.0-v3346</version>
>
> if you only want this specific version?
>
> Regards,
> > Sandeep.
> >
>
>
>
> --
> Cheers, Stuart
>
>
>
>
> --
> Cheers, Stuart
>



-- 
Cheers, Stuart