answered to your other thread about it. You need to use dependencyManagement in maven 2.0.9+ to force the versions when Maven doesnt resolve the ranges as Eclipse expects
I will post soon the material from the tutorial I gave at EclipseCON covering that and other issues with Maven and OSGi http://www.jroller.com/carlossg/entry/letters_from_eclipsecon On Tue, Mar 18, 2008 at 1:13 PM, Apaar Trivedi <[EMAIL PROTECTED]> wrote: > I have looked into this a bit more and it appears that the problem is > with the qualifiers getting added to the versions of the artifacts > deployed by the eclipse:to-maven target. The solution involves allowing > the 'stripQualifier' parameter to be exposed in the plugin, here is a > note I sent to the dev list: > > We need one thing parameterized on the EclipseToMavenMojo.java in the > maven-eclipse-plugin which should be parameterized anyway. In the call > to osgiVersionToMavenVersion, it only allows 'false' to be passed in for > the 'strip qualifier' parameter. > > While the make-artifacts (which extends to-maven) target allows you to > strip the qualifier, this is not a parameter that can be used in the > to-maven target. This is a problem because using 'to-maven' provides > artifacts with the proper names but the dependecies do not resolve due > to the qualifiers on the versions. While make-artifacts provides > dependecies that resolve but the naming convention of the groupId's and > artifactId's is incorrect. > > Just a parameter -DstripQualifer that gets passed in to the call to > osgiVersionToMavenVersion( String version, String forcedQualifier, > boolean stripQualifier ) would be perfect. > > > Thank you > Apaar > > > > > -----Original Message----- > From: Apaar Trivedi [mailto:[EMAIL PROTECTED] > Sent: Tuesday, March 18, 2008 1:28 PM > To: [email protected] > Subject: Versioning conflict in mvn and eclipse:to-maven plugin > > Hey guys, i believe there is a bug in either the way versions for > dependencies are matched or in the way the eclipse:to-maven plugin > works. > > When I run the eclipse:to-maven target, my brand new repository is > populated with eclipse plugins and nothing else. I attempt to build a > project which depends on these dependencies, but the dependencies do not > resolve. One of the eclipse plugins depends on another one that is > within version range [3.3.0,4.00). The dependecny i have to satisfy > this version is 3.3.0-3.3.0-I20070605-0010. But this is not acceptable, > yielding this error: > > org.apache.maven.lifecycle.LifecycleExecutionException: Couldn't find a > version in [3.3.0-I20070605-0010, 3.2.0-I20060605-1400] to match range > [3.3.0,4.0.0) > > I understand that maven might desire some sort of special versioning in > the form of x.y.z, in which case the eclipse:to-maven plugin should > setup the pom's correctly (set the versions in an acceptable manner.) If > maven does not have this hard and fast version requirement, shouldn't it > accept the version 3.3.0-I20070605-0010, 3.2.0-I20060605-1400 to be > within 3.3.0-4.0.0? > > Thank you > Apaar Trivedi > Consultant > Blue Fish Development Group > http://www.bluefishgroup.com <http://www.bluefishgroup.com/> Blue Fish > is Hiring! Check out www.bluefishgroup.com/careers > <http://www.bluefishgroup.com/careers> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
