Re: [m2e-users] eclipse:clean and eclipse:eclipse on parent pom.xml

[Jason van Zyl <jason@xxxxxxxx>]

The use of the maven-eclipse-plugin (eclipse:eclipse, eclipse:clean) is not supported with m2eclipse. You either use m2eclipse on its own or use, or use the maven-eclipse-plugin on its own as they are not meant to work together. If you use m2eclipse you Import --> Maven --> Existing Maven Project to get the project in the workspace.

On Jul 9, 2012, at 8:18 PM, Alexandru Geană wrote:

Hello everyone,

Sorry if this questions sounds awkward, but I'm trying to understand how things work with m2e. I have two maven projects, one being the parent and the other being the child. In eclipse, whenever I run any of the two goals stated (eclipse:clean and eclipse:eclipse), they only seem to work on the child and never on the parent. For example, there is a .project file for the parent which doesn't go away when I run eclipse:clean; also if I delete it manually, it doesn`t appear when I do eclipse:eclipse.

Furthermore, the .settings folder never gets affected for neither the parent, nor the child. From my understanding, the eclipse:clean goal should delete the .project, .classpath, .wtpmodules files and .settings folder whereas eclipse:eclipse should create it.

Am I doing something wrong or... ? I would very much appreciate if someone could give me a hint or point me in the right direction.

Best regards,

Alex G.

E-mail address: alex@xxxxxxxxxx

_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder,  Apache Maven

http://twitter.com/jvanzyl
---------------------------------------------------------

A language that doesn’t affect the way you think about programming is not worth knowing. 
 
 -- Alan Perlis