"adrian(a)jboss.org wrote : It's not a vote. Either make a logical argument or go join some Apache project where you can make these usless comments to your hearts content. :-) We get it, Adrian, you're intimidating. I'll spell it out, then. Adding .classpath and .project files to the repo might seem like a convenience to users of the Eclipse IDE, but actuality what we're doing here is introducing elements that are unbound to actual changes in the POM, and may be misleading. By guaranteeing a build that will function from the command-line only, we add a fail-fast; compilation WILL fail in IDEs. It becomes the responsibility of the developer to add extensions to make it work in their preferred environment. And with the maven commands I've illustrated, it's incredibly simply to do so with Eclipse. We can even bind it to the build lifecycle in an Eclipse profile if we'd like. Generated code in a central repo is redundant and easily outdated. And users of IntelliJ (like Ales) shouldn't have to worry about the CP of Eclipse users. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133287#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...