On Thu, Apr 3, 2008 at 4:15 PM, WolfgangRoessler <[EMAIL PROTECTED]> wrote: > > Hello, > > I have a problem when using eclipse:to-maven. For example > org.eclipse.emf:ecore has a dependency to org.eclipse.runtime:core with a > version range [3.2.0,4.00). Unfortunately the version of > org.eclipse.runtime:core is something like 3.2.0-v20071103 so maven can't > resolve the version. Are there any solutions for this problem? (except for > using make-artifacts which generates different artifactIds).
Not that I can tell. I had to use make-artifacts for exactly this reason (there is another post about it recently). The good news is that while the pom groupId:artifactId:versionId doesn't include the qualifier the eclipse:install-plugins does copy the non-qualified jars to the correctly qualified jar name. There is another post by Jason indicating that maven and eclipse should be defining how to unify the maven/eclipse version bridge. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
