[ https://jira.codehaus.org/browse/MECLIPSE-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=302242#comment-302242 ]
Joachim Breuer commented on MECLIPSE-728: ----------------------------------------- The last version of the maven-eclipse-plugin where resolveVersionRanges appears to work seems to be 2.4. > resolveVersionRanges option of make-artifacts does nothing > ---------------------------------------------------------- > > Key: MECLIPSE-728 > URL: https://jira.codehaus.org/browse/MECLIPSE-728 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Affects Versions: 2.9 > Reporter: Joachim Breuer > > When running > mvn eclipse:make-artifacts -DresolveVersionRanges=true > .poms with very wide dependency version ranges are written, exactly the same > as for -DresolveVersionRanges=false. > This causes eclipse 3.5.2 artifacts to partially pull eclipse 4.2 > dependencies, which breaks all sorts of things in "interesting" ways. > I cannot find a way with the current make-artifacts to have both eclipse > 3.5.2 and eclipse 4.2 artifacts visible in the same artifact mirror without > mutual interference. > Looking at the code, it appears that > org.apache.maven.plugin.eclipse.MakeArtifactsMojo.resolveVersionRanges(Model, > Map) is not called from anywhere. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira