[ http://jira.codehaus.org/browse/MNGECLIPSE-58?page=comments#action_61238 ]
Mark J. Sinke commented on MNGECLIPSE-58: ----------------------------------------- Please note that I added a patch to MNGECLIPSE-59 to solve Eclipse Workspace artifact lookup. > Ignore dependent projects when building project classpath > --------------------------------------------------------- > > Key: MNGECLIPSE-58 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-58 > Project: Maven 2.x Extension for Eclipse > Type: Improvement > Components: Dependency Resolver > Versions: 0.0.4 > Environment: Eclipse 3.1.1, MyEclipse 4.0.3, Windows XP2, Java 1.5.0_06 > Reporter: Leonardo Quijano Vincenzi > Assignee: Eugene Kuleshov > > > When using MyEclipse's deployer to deploy a webapp with dependant projects, > my dependent projects get included twice. For example, if my web app is > FooWeb, and it depends on FooBusiness, and MyEclipse's smart deploying is > enabled, the final web-app distribution is like this: > /WEB-INF > /classes > FooWeb.class > FooBusiness.class > /lib > FooBusiness-VERSION.jar > That means that some resources that are intended to be included once (usually > for classpath scanners) are included several times. It also could cause some > problems when updating the dependant project in eclipse, but not running "mvn > install". > M2ECLIPSE's classpath resolver could skip dependant projects that are > Maven-enabled when building the classpath, to avoid this double dependency > problem and to avoid having stale JARs included in the WEB-INF/lib directory > of deployed projects. -- 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
