Zu einem Posting auf http://java.dzone.com in der javalobby musste ich dann doch noch etwas kommentieren..
"A yes or no answer seems to be a little bit to easy to me. It depends on. If you work in a homogenous infrastructure where every developer has to use the same IDE it makes sense to me, also to reuse the projects settings. The costs for configuring an IDE-project correctly are not that low. We use eclipse projects that make use of more than 30 external libraries. If you want to work properly with them, use the debugger etc, you have to configure their sourcecode and javadoc location. I'am not a maven-expert, but I think a *.pom file would not automatically deliver this information to the IDE of your choice. For an eclipse project in a homogenous IDE infrastructure it makes also sense to me to check in the code-templates, compiler warning- and compliance- settings. So I would choose an pragmatic approach and first check the benefits and the costs and then decide what should be placed under version control and what not.
Nevertheless, in my point of view there should be additionally buildfiles (ant,maven,bat,sh or what else ) to create the project via commandline or your continues integration tool that are placed under version control, too. The goal should be that an developer can easy load a project within his IDE to maintain the project and that he can easy build the projects artefacts via commandline or ci-tool."
