.classpath 和 .project - 是否检查版本控制? [英] .classpath and .project - check into version control or not?

问题描述

我正在运行一个开源 Java 项目，该项目由依赖关系树中的多个模块组成.所有这些模块都是 subversion 存储库中的子目录.对于我们项目的新手来说，在 eclipse 中手动设置所有这些需要做很多工作.

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.

并非我们所有的开发人员都使用 Eclipse.尽管如此，我们正在考虑只检查 .classpath 和 .project 文件以帮助新手入门.这是一个好主意吗?还是会导致这些文件中不断发生冲突?有没有其他方法可以让项目在 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?

推荐答案

绝对是的，正如我在您是否将项目文件置于版本控制之下?"

加载，设置，开始."

但是...这实际上仅适用于最近的 Eclipse3.5 设置，其中构建路径支持相对路径:

But... this is actually true only for recent Eclipse3.5 settings, where build paths support relative paths:

Eclipse3.6会更好，因为它支持链接资源中路径变量的相对路径:

And Eclipse3.6 would be better, as it supports relative paths for path variables in Linked Resources:

(从 3.6M5 开始)

(since 3.6M5)

这篇关于.classpath 和 .project - 是否检查版本控制?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！