"wolfc" wrote : The .classpath files must not contain a reference to a workspace project, because a different version might be in use. So generating them with the aggregator is a no-go. Thanks for pointing this out; I hadn't noticed that. It's gotta be a simple fix to enhance this Mojo to add a property "-Dmaven.eclipse.noProjectRefs" and override this behavior, no? "wolfc" wrote : I somewhat like the idea of using M2 Eclipse plugin but ... | dependency resolution ... different versus Maven builds | ...makes it unusable. It's still a good tool. Eclipse classpath has been different from compile or JUnit classpaths for a long time anyway. So we do what we always do...code in it, and run builds from the command-line before checking in. I'd sent out licenses to the EJB3 team for IntelliJ, which is supposed to have better Maven support. I haven't found the energy to fight habits and give it a good try yet. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133792#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...