[ http://jira.codehaus.org/browse/MECLIPSE-32?page=comments#action_76883 ] Kenney Westerhof commented on MECLIPSE-32: ------------------------------------------
Hm. Not sure I like this solution in this case. I've got the same issue here - when importing the m2 source tree and plexus, and I wouldn't want to update the m2 poms with eclipse plexus config ;) You can just use the reactor: mvn eclipse:eclipse -r -Dmaven.reactor.includes=root/pom.xml,path/to/backport-util/pom.xml If this is sufficient we could close this issue. > Allow for forcing the creation of direct project references for dependencies > ---------------------------------------------------------------------------- > > Key: MECLIPSE-32 > URL: http://jira.codehaus.org/browse/MECLIPSE-32 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement > Components: multiproject > Affects Versions: 2.0 > Reporter: Barry Kaplan > > For some thirdparty dependencies, it is common (for me at least) that an > eclipse project for that dependency does/will exist in the workspace. It > would be nice if dependencies in eclipse projects can be forced to use a > direct project reference. eg: > <dependency> > <groupId>backport-util-concurrent</groupId> > <artifactId>backport-util-concurrent</artifactId> > <version>2.0_01_pd</version> > <scope>runtime</scope> > <properties> > <property name="eclipse.dependencyType" value="XXXX"/> > </properties> > </dependency> > Where XXXX can be: > - 'project' -- always create a project reference > - 'jar' -- always create a jar reference as in MNG-955 > - 'auto' -- the behavior prior to MNG-955 -- 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
