[ http://jira.codehaus.org/browse/MECLIPSE-40?page=comments#action_67255 ]
David Boden commented on MECLIPSE-40: ------------------------------------- If you build by pointing at the aggregated pom.xml, the eclipse plugin will setup the project relationships as you'd expect. You actually have to turn this behaviour off if you don't want it, using the useProjectReferences configuration option. Please close this issue, I believe that it is no longer relevant. > Multi project dependencies should not require eclipse project names to be the > artifactId > ---------------------------------------------------------------------------------------- > > Key: MECLIPSE-40 > URL: http://jira.codehaus.org/browse/MECLIPSE-40 > Project: Maven 2.x Eclipse Plugin > Type: Improvement > Versions: 2.0 > Reporter: Dave Sann > > > Multi project dependencies should not require eclipse project names to be the > artifactId > eg: > eclipse workspace: > > Project1 -> creates artifact-x > > Protect2 -> creates artifact-y, depends on artifact-x > > MultiBuild - to build a selected collection of checked out projects > >> pom.xml includes, > ... > <modules> > <module>../Project1</module> > <module>../Project2</module> > <modules> > ... > eclipse:eclipse will create a depencency to a project named artifact-x, where > it should create a dependency to Project1 -- 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
