My question is about the differences between the M2 Eclipse Plugin and the plain old command line M2 version. What advantages does the plugin provide? I checked out a project (Apache Tusqany) into my eclipse workspace. I have the M2 plugin installed - on the console I see:
2/13/06 8:13:53 PM EST: Local repository folder "" does not exist 2/13/06 8:13:54 PM EST: [DEBUG] Found 0 components to load on start 2/13/06 8:13:54 PM EST: [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and Settings\Administrator\.m2\plugin-registry.xml' 2/13/06 8:13:54 PM EST: [DEBUG] Building Maven global-level settings from: 'C:\eclipse-SDK-3.1.1\eclipse\conf\settings.xml' 2/13/06 8:13:54 PM EST: [DEBUG] Building Maven user-level settings from: 'C:\Documents and Settings\Administrator\.m2\settings.xml' 2/13/06 8:13:54 PM EST: Reading /Tusqany/pom.xml 2/13/06 8:13:54 PM EST: Local repository folder "" does not exist 2/13/06 8:13:54 PM EST: [DEBUG] Found 0 components to load on start 2/13/06 8:13:55 PM EST: [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and Settings\Administrator\.m2\plugin-registry.xml' 2/13/06 8:13:55 PM EST: [DEBUG] Building Maven global-level settings from: 'C:\eclipse-SDK-3.1.1\eclipse\conf\settings.xml' 2/13/06 8:13:55 PM EST: [DEBUG] Building Maven user-level settings from: 'C:\Documents and Settings\Administrator\.m2\settings.xml' 2/13/06 8:13:55 PM EST: [DEBUG] org.apache.tuscany:tuscany-project:pom:SNAPSHOT (selected for null) 2/13/06 8:13:55 PM EST: Reading /Tusqany/spec/pom.xml *snip* And basically nothing gets built. If I run the command line version right against the tree directly, everything builds like a champ. Am I lacking some eclipse setup to make this work? I simply checked out the code into the workspace as a 'project'. Thanks, Scott.