Should Eclipse-specific files in an VCS be ignored, if using Maven?

Question

I know why not to commit Eclipse/IDE-specific files into a VCS like Git (which I am actually using). That is one of the reasons I am using Maven and having it generating these f

Answer 1

usually .project and .settings/ should likley be versioned and ignored!

.classpath and target should not be versioned but ignored.

This is a first inital boot-up on checkout-practice.

i.e.

• You told everone to use four spaces as tab, this information is stored under .settings/xxx
• but you give no restriction where they have to install their tomcat/jdk's (stored under .classpath)

ok?