"ALRubinger" wrote : "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. | No just don't have time to read drivel :-) anonymous wrote : | 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 We'll continue to disagree. Technical * It's called an I(ntegrated)DE for a reason * "Baby sitting" builds and tools is not what I want to do * Remembering and performing recipes of many tool procedures is not productive (it's a good job I know how to program bash, but that's just a hack around the problem :-) * Eclipse is what I use, we can do the same for Intellij (actually I don't use eclipse as much as I could because sometimes it is just too painful) * Checking in the eclipse files in svn makes little difference in practice unless everybody updates them you have to run mvn eclipse:eclipse anyway. It's just you have N updaters running it instead of one committer. Philosophy * Redundancy is only a problem when it leads to error or reduced performance * Redundancy to improve performance and reduce error is a good thing * Claiming that it can lead to error in checking .classpath files because the real problem is in maven/eclipse not being able to understand each other mistates where the problem lies. * When it annoys me enough, I'll fix the real problem, in the meantime it's workarounds and lots of hair pulling :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133299#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...