.classpath and .project - check into version control or not?
Posted
by amarillion
on Stack Overflow
See other posts from Stack Overflow
or by amarillion
Published on 2010-05-12T11:17:38Z
Indexed on
2010/05/12
13:14 UTC
Read the original article
Hit count: 237
I'm running an open source java project that consists of multiple modules in a tree of dependencies. All those modules are subdirectories in a subversion repository. For newcomers to our project, it's a lot of work to set all that up manually in eclipse.
Not all our developers use eclipse. Nevertheless, we're considering to just check in the .classpath and .project files to help newcomers to get started. Is this a good idea? Or would that lead to constant conflicts in those files? Is there an alternative way to make the project easy to set up on eclipse?
© Stack Overflow or respective owner