- http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133184#... "adrian(a)jboss.org" wrote : | 2) Update the relevant .classpath files | | ... | | (2) is optional, but it would be friendly, otherwise we end up with different | subprojects referencing different versions (e.g. because only one uses a new feature) | and Eclipse gets confused when running tests or showing source. | Rather than friendly, I see this as unnecessary. OK, I guess this was very useful for the projects that didn't have Maven handling the build or any other means of producing the project files. I know I would like to have something like that for AS_trunk and IntelliJ. ;-) But in our case, it's nothing more than additional work. Not to sound rude, but why should we care about .classpath files and not any other IDE project files? I bet there is a Maven --> (your) IDE plugin available, so let's all use that and drop those .classpath files. Not to mention that if we still decide to support them, we're bypassing what Maven poms actually hold as dependencies, possibly resulting in inconsistency between poms and .classpath. I'm always in favor of not keeping things around that can be generated. And we're doing that with javacc, so why the change-of-heart here? ;-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133189#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...