[ http://jira.codehaus.org/browse/MECLIPSE-40?page=comments#action_68880 ]
Dave Sann commented on MECLIPSE-40: ----------------------------------- I disagree. I do want project references. but the plugin does not behave as I would expect. If I build the projects above using the aggregated pom.xml I end up with a broken set of project dependencies. the reason is that the project references (in the above example) should be to Project1 (the local name) but the plugin creates dependencies to a non existant project called artifact-x. I have updated the eclipse plugin today and this feature is still present. This makes it extremely hard to use maven with eclipse. > 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
