Java project: should .classpath .project file be committed into repository? [duplicate]

Answer 1

We check in .project and .classpath. With ProjectSet's this allows us to check out complex workspaces with a single "Import Team ProjectSet"

Answer 2

Not checking in .project file will make my development less efficient (I can't simply "import" a project code from a directory)

for this issue, you can choose to create new project and import existing source.

one issue with IDE specific files like .project is that other Developers may want to use another IDE do develop the project, so they may add another type of project files. this will make your repo messy.

Answer 3

There is not problem of checking in .classpath and .project files into repository. It will help developers which use Eclipse to get going faster.

Warning: Make sure your .classpath file is referencing only artifacts which either checked into the repository with the project or can be obtained automatically (such as maven artifacts).

Answer 4

The key question with all such files is "Can they be reproduced automatically?" If not, check them into source control.

In this case, I'd say "yes," unless you're using maven, which has m2eclipse and the eclipse plugin to generate them for you.