[ http://jira.codehaus.org/browse/MNGECLIPSE-19?page=comments#action_64965 ]
darren hartford commented on MNGECLIPSE-19: ------------------------------------------- I think you need to look at the pom.xml's in the image and swap - the child POM on the left, the parent POM on the right (the one that should be downloaded by Maven), not the other way around. Basically need to evaluate dependencies on the 'effective-POM'. This is an issue. > version can not be supplied in parent pom > ----------------------------------------- > > Key: MNGECLIPSE-19 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-19 > Project: Maven 2.x Extension for Eclipse > Type: Bug > Versions: 0.0.3 > Reporter: Lee Meador > Assignee: Dmitri Maximovich > Fix For: 1.0.0 > Attachments: MNGECLIPSE-19.jpg, test-projects-MNGECLIPSE-19.zip > > > If I don't have a <version> tag in the POM, I get an eclipse error with its > little red spot on the top line of the POM. The maven dependencies all > disappear (and, of course, most everything won't compile any more). > The version should be gotten from the parent POM but doesn't seem to be. > Interestingly enough, the first dependency with no version (jmock) seems to > be ok. The message on the red spot on the pom does not mention jmock. It does > mention all three of the spring dependencies that follow it. -- 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
