Jim, The m2 plugin replaces the normal eclipse build system with maven. If you want to use M2 then you don't need to run mvn eclipse:eclipse at all. What mvn eclipse:eclipse does is it generates source code, and produces a .project and .classpath so that eclipse can use it's normal build system not work. The two approaches are not really compatible with each other.
--Bobby On 8/29/11 11:52 AM, "Jim Falgout" <[email protected]> wrote: Using the latest trunk code, used the "mvn eclipse:eclipse" target to build the Eclipse project files. I've got the M2E plugin for Maven installed. After some trouble with lifecycle errors ("Plugin execution not covered by lifecycle configuration" error messages) I noticed this comment in the .project file: "NO_M2ECLIPSE_SUPPORT: Project files created with the maven-eclipse-plugin are not supported in M2Eclipse". Is there another recommendation for Maven integration using an Eclipse plugin that will work out of the box? Thanks!
