The Roo "perform eclipse" command uses the mvn:eclipse plugin to generate Eclipse project metadata. However, most developers today prefer to use the Sonatype m2eclipse Eclipse plugin instead. m2Eclipse also comes bundled with STS, is used in SpringSource training courses, and used in all Spring 3 sample applications/tutorials.
As a user, I would like to see a Roo command that generates Eclipse metadata for my project with Spring and m2Eclipse project natures configured. Currently, if I use "perform eclipse" the mvn:eclipse plugin generates a Eclipse project build path entry for each .pom dependency referencing the M2_REPO classpath variable. This conflicts with m2eclipse's "Maven Dependencies" classpath container, which is generally preferred and easier to manage.
New Feature
Closed
Major
