"adrian(a)jboss.org wrote : How is it different to what you suggest (no .classpath file or an old one they generated before doing the svn update?) Fail-fast. No .classpath is very obviously wrong in Eclipse. An incorrect .classpath might pose as correct (pointing to wrong versions, perhaps). Though I still disagree with storing gen'd files in SCM, I can live with the addition of a Mojo/Plugin to autorun eclipse:eclipse. At the end of the day, this is developer preference, we're debating the architecture of .classpath here. :) "adrian(a)jboss.org" wrote : Of course the real fix is to replace eclipse's java project bundle with an extended one that runs off the pom.xml instead of .classpath ;-) Max/Culpepper/Stryker...get on it. :D S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133344#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...