Hi, Background: Trying to mavenize an Eclipse Plugin project, I got error messages like the following: Couldn't find a version in [1.0.0-v20070606] to match range [1.0.0,2.0.0) I put in jira a test project to reproduce this error [1].
Discussions: After some investigations: * the error comes from transitive dependencies (BTW I updated DefaultArtifactCollector (r647445) to have the dependency trail). * a version without qualifier is newer than a version with qualifier, i.e in our case 1.0.0 is newer than 1.0.0-v20070606 (see also [2] [3]). This logic is valid for alpha, beta (i.e. 1.0-alpha-1 < 1.0) but not for Eclipse artifacts. * Carlos in [4] suggested to use exclusions or dependencyManagement. With this approach, POM will quickly become ugly (see for instance ASF Directory Studio POM [6]). Moreover, the actual repo is just unusable because transitive dependencies are not resolved at all due to the current logic. * Using eclipse:to-maven doesn't help [5] So, how to make the Eclipse repo workable for an Eclipse project? A solution could be done in [1], but this might be Eclipse specific. At least, the repo will work :) Thoughts? Vincent [1] http://jira.codehaus.org/browse/MNG-3518 [2] http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution#DependencyMediationandConflictResolution-DependencyVersionRanges [3] http://docs.codehaus.org/display/MAVEN/Versioning [4] http://www.nabble.com/Re%3A-in-repo1-it-is-available-td13950144s177.html#a14708458 [5] http://www.nabble.com/Couldn%27t-find-a-version-when-building-pde-maven-plugin-td16116114s177.html [6] http://svn.apache.org/repos/asf/directory/studio/trunk/pom.xml --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
