Geek Answers Handbook

Is it good practice to include Eclipse project files with sources in SCM?

We have a rather complicated multi-module Maven project. There are Flex modules, GWT modules, Java modules, and a number of WAR modules. To simply process the import of these projects into Eclipse, historically we have included all the relevant Eclipse project files in the source tree.

However, in the past this was a source of problems, because sometimes these files were accidentally changed and checked ... thus creating problems for other developers. With the advent of M2E and its new support for configurators to help customize Eclipse projects upon import, we are redefining this strategy.

In general, do projects include these Eclipse files in Subversion / Git / etc?

+5
source share
4 answers

The answer to the upper level: it is completely a matter of taste :-)

Personally for "internal" projects (you have some control over other developers' environments), I include Eclipse files with the caution that you must be sure that everyone uses relative paths in their configurations. (Every few months we had a build break because the library path was hard-coded, it took a few seconds, but it was unpleasant.) I also usually used a lot of things like Eclipse code formatting and compiler warnings to simplify life (for example, huge Subversion checks, because one of the editors fell into the battle for formatting tabs).

, , Eclipse Subversion , .project /. , Eclipse ( , , Ant Make).

(: (sic?) Eclipse), "" . "" , , , MicroSoft Visual Studio .project, ad-hoc, " " . Subversion ...

" " . .

svn://someplace.nn/projects/MyProject/trunk —> source
svn://someplace.nn/projects/MyProject.control/trunk —> project control files

, GPL , GPL... GPL .project , " Eclipse, () Subversion, . ( , ...)

+2

SCM. .project URI, . .project .

+3

() , , .project SCM. , .. . , Eclipse.

, Checkstyle , : -).

.project, .classpath,.checkstyle, .settings.

, , , , , , , checkstyle. , , , , SCM. , ?

FOSS - IDE.

+3

maven-eclipse pom. , eclipse .

also, if you have common eclipse related files (or eclipse plugin), you can define them in maven-eclipse-plugin too. for example checkstyle.xml, codeTemplate.xml, codeFormatter.xml .... saving these files to scm might be a good idea.

+2
source

More articles:


All Articles