dependencyManagement in parent poms broken in eclipse on linux --------------------------------------------------------------
Key: MNGECLIPSE-145 URL: http://jira.codehaus.org/browse/MNGECLIPSE-145 Project: Maven 2.x Extension for Eclipse Type: Bug Components: Dependency Resolver Versions: 0.0.9 Reporter: Scott Cytacki Assigned to: Eugene Kuleshov Attachments: pom.xml This is a weird one. I don't know if it is a maven embedder bug or an eclipse plugin bug. I attached a test pom. This pom has a single dependency on org.codehaus.xfire:xfire-java5 >From the command line I can run mvn compile and it downloads the correct xfire >artifacts. I tried it both with maven 2.0.2 and 2.0.4 When I enable maven on the project in eclipse using 0.0.9 maven plugin, eclipse 3.2RC5, linux. It fails saying it cant find: org.codehaus.xfire:xfire-core:jar:2.4.1 org.codehaus.xfire:xfire-aegis:jar:2.4.1 org.codehaus.xfire:xfire-annotations:jar:2.4.1 When I try the same thing on maven plugin 0.0.9, eclipse 3.2RC7, intel mac. It works fine. I looked into the xfire poms, and they are using a fancy dependency setup. xfire-java5 dependends on xfire-core but it doesn't specifiy a version number. The version is supposed to be pulled from the dependency management in the parent pom: xfire-parent. Actually the dependency management section of the xfire-parent doesn't have the version for each dependency instead it uses: ${version}. Which I assume pulles the version from xfire-parent itself. So some how this double indirection of version number is confusing only linux. It could also be the version of eclipse. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira