Maven Integration for Eclipse

dependencyManagement in parent poms broken in eclipse on linux

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Duplicate
  • Affects Version/s: 0.0.9
  • Fix Version/s: None
  • Component/s: Dependency Resolver
  • Labels:
    None
  • Number of attachments :
    1

Description

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.

Issue Links

This issue duplicates:
MNG-2653 using ${version} for subproject dependencies doesn't work (maven uses 2.4.1 version instead) Major Closed

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
vincenzo cerbone added a comment -

I had also the same problem on a project of my own. It happens when I specify the ${project.version} as version on a father POM in the section dependencyManagement for children POMs (so that children inherit it without having to declare it again..)

Show
vincenzo cerbone added a comment - I had also the same problem on a project of my own. It happens when I specify the ${project.version} as version on a father POM in the section dependencyManagement for children POMs (so that children inherit it without having to declare it again..)
Hide
Permalink
Eugene Kuleshov added a comment -

Jason, this must be embedder issue or something plarform specific. I saw this magic "2.4.1" version before and that comes from out of nowhere...

Show
Eugene Kuleshov added a comment - Jason, this must be embedder issue or something plarform specific. I saw this magic "2.4.1" version before and that comes from out of nowhere...
Hide
Permalink
David Levy added a comment -

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.

Show
David Levy added a comment - 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.

People

Vote (2)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.