You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "David Levy (JIRA)" <ji...@codehaus.org> on 2006/12/06 01:38:41 UTC
[jira] Commented: (MNGECLIPSE-145) dependencyManagement in parent
poms broken in eclipse on linux
[ http://jira.codehaus.org/browse/MNGECLIPSE-145?page=comments#action_81850 ]
David Levy commented on MNGECLIPSE-145:
---------------------------------------
I've run into this bug before and never found out a reason why... but this time I managed to correlate the occurrence of the bug to when I down shifted my JDK to 1.4.2 from 1.5. Suddenly this bug was occuring whenever I tried to build my projects. When I changed my system path and restarted eclipse, it disappeared.
Without knowing much more about what's going under the hood, maybe it's a quirk dependency on the version of the JDK - and the magic number 2.4.1 just happens to be the reverse of 1.4.2... without knowing what's going on under the hood it could just be coincidence, but you may want to investigate along that line, just in case.
Cheers, hope you get this one solved, it's annoying as hell when it happens seemingly for no reason.
> 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
> Issue Type: Bug
> Components: Dependency Resolver
> Affects Versions: 0.0.9
> Reporter: Scott Cytacki
> Assigned To: Jason van Zyl
> 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