Hi, i did hit the same problem and found that there is a difference in the version range handling between maven and eclipse plugins.
My solution was rather "ugly" i used the maven-eclipse-plugin in the version 2.4 to create a local repository. because that version of the plugin ignores the version ranges and makes hard links between the versions. mvn org.apache.maven.plugins:maven-eclipse-plugin:2.4:to-maven But the real question will be for Carlos Sanchez (who wrote new version ranges as far as i know). How to resolve these version ranges with maven in the correct way. Maven rules specify that the version 3.3.0-v20070604 is before 3.3.0 and not after, as eclipse resolves them.... Carlos what do you say to this problem? regards, Ritchie Jeroen Lankheet wrote: > Hi, > > I need to change the Ant build target for the pde-maven-plugin. > So I checked out the trunk, changed version 2.0.9-SNAPSHOT into 2.0.8 in the > POM > and did a mvn clean install. > The following error came up: > > [ERROR] BUILD ERROR > [INFO] > ------------------------------------------------------------------------ > [INFO] Failed to resolve artifact. > > Couldn't find a version in [3.3.0-v20070604, 3.2.1-R32x_v20060914] to match > range [3.3.0,4.0.0) > org.eclipse.core:resources:jar:null > > from the specified remote repositories: > codehaus.org (http://snapshots.repository.codehaus.org), > central (http://repo1.maven.org/maven2), > internal > (file:////notorious.ehv.apptech.philips.com/aurora/MavenRepository) > > The org.eclipse.core.resources plugin has version 3.3.0-v20070604. > That is a match isn't it? > > Regards, > Jeroen Lankheet --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
