Hello, some MECLIPSE issues are related to the phase executed by the eclipse plugin to collect generated-* folders.
Here is a simple example of the side-effect of this strategy pom.xml |_ ear project |_ jar project |_ war project Lets supose the jar project is broken and can't compile. Checking the project from svn and running mvn eclipse:eclipse fails, as the maven-ear-plugin has @RequireDependencyResolustion(test) (is this really required ?) on GenerateApplicationXMLMojo mvn install also fails as the jar plugin is broken There is NO way to configure eclipse and fix the project ! My first idea is to find some hook in the ArtifactResolver (or other) to register the multiproject modules as "fake" artifacts, so that dependency resolution doesn't fail. I looked at DefaultArtifactResolver ... but is far too complex for me and can't find where the Artifact objects are created, and how the associated File object could be hacked A cleaner fix would be to have an early phase for generate-* Mojos to register generated folders... but hits requires changes on most plugins - maybe could be planned for maven 2.1 ? Any suggestion ? Nico.
