[ http://jira.codehaus.org/browse/MNG-955?page=comments#action_48424 ]
Rafal Krzewski commented on MNG-955: ------------------------------------ Using eclipse project references is the right thing to do in 99% cases IMO. It gives you point-and-click navigation over the up-to-date sources. You could use resource sets to limit the number of projects displayed in the navigators, or try the upcoming Mylar plugin. The option to handle the remaining 1% border cases would be nice though, M1 version has such functionality: <eclipse.dependency>false</eclipse.dependency> property on a a project's dependency item. > There should be possible to use artifacts instead of project references in > multi module projects > ------------------------------------------------------------------------------------------------ > > Key: MNG-955 > URL: http://jira.codehaus.org/browse/MNG-955 > Project: Maven 2 > Type: Bug > Components: maven-eclipse-plugin > Reporter: Kaare Nilsen > Fix For: 2.0-beta-4 > > > One of the fine things with maven is that one can have several modules in a > project. > But in the eclipse plugin all dependent modules in the project is added as a > project reference instead of using the delivered artifact. > As a result i have to have all my modules (eclipse projects) opened just to > compile in eclipse. > I think this should be an option. e.g. > <useProjectReference>true</useProjectReference> > with this set to true as default, but when false, the classpath should use a > reference to the jar in local repos as all other artifacts -- 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
