Hi, We have eclipse:eclipse as the default goal for "eclipse" profile (-Peclipse). The "eclipse" profile gives us a bit control, for example, some plugins won't be activated under that profile as "eclipse:eclipse" will trigger all the plugins using "generate-resources" phase.
I also remember that we use "eclipse" profile to work around an issue related to the the NOTICE/LICENSE file in the root of the project. But it seems that the latest Eclipse plugin can handle the source folder overlapping and exclusion now. Thanks, Raymond From: ant elder Sent: Friday, January 30, 2009 9:55 AM To: [email protected] Subject: Re: svn commit: r739245 - /tuscany/java/sca/modules/core/pom.xml [snip] Hi Ant You don't need eclipse:eclipse anymore. Give mvn -Peclipse a try and see if that helps. Is there a reason we have to do this with a -Peclipse (sorry if its obvious I've not looked at all how this is setup), it would be nice if we could keep the "mvn eclipse:eclipse" standard instead of using our own special way. ...ant
