There are discrepancies with version ranges between Maven and OSGi. Not much to do as i don't think anybody will go through all Eclipse plugins and update the poms manually. At least for now you can use exclusions, or force the versions you want in dependencyManagement
On Dec 29, 2007 9:48 AM, Felix Knecht <[EMAIL PROTECTED]> wrote: > Carlos Sanchez schrieb: > > that's right, I still have to polish the eclipse plugin to generate > > the Eclipse repo using some "conventions" > > > > I tried to build 'my' repo for the eclipse-3.3.1.1 version using > maven-eclipse-plugin build from trunk with mvn > eclipse:to-maven. All worked well and the artifacts were deployed to were > expected. > > Trying to use them later on I run into the following problem: > > Couldn't find a version in [3.3.0-v20070606-0010, 3.2.0-v20060605-1400, > 3.3.0-v20070531-1300] to match range [3.3.0,4.0.0) > org.eclipse:text:jar:null > > Doing some search about this I found a thread [1] saying that 3.3.0-xxx is > less than 3.3.0 (what would explain my problems). > Is this an issue of the match range checker or an issue of the pom.xml > creation of the eclipse:to-maven goal? > > > Thanks and regards > Felix > > [1] http://www.nabble.com/OverConstrainedVersionException-td14289478s177.html > > > --------------------------------------------------------------------- > 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]
