我应该提交由eclipse更改的文件 [英] Should I commit files that are changed by eclipse

查看:125
本文介绍了我应该提交由eclipse更改的文件的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我以eclipse项目的形式继承了一个java项目。更改tomcat配置(从v6到v7)后,subclipse会提示我提交以下文件。




  • .classpath

  • org.eclipse.core.prefs

  • org.eclipse.common.project.facet.core.refs

  • org.eclipse .common.project.facet.core.xml



会提交他们帮助我的团队成员还是会混乱他们的工作区? p>

最佳做法是什么?

解决方案

一般而言,您应该检查(并在更改之后提交)对构建有贡献的所有内容,并且完全重新构建不能重新生成,并且是特定于工作站的。 (这个陈述的含义取决于你的构建过程/过程,这是打算的。)



这意味着你应该排除在完整构建后重新生成的所有内容。所以没有办理入住手续(不提供办理入住手续)。


I inherited a java project in the form of an eclipse project. After changing the tomcat configuration (from v6 to v7), subclipse prompted me to commit the following files

  • .classpath
  • org.eclipse.core.prefs
  • org.eclipse.common.project.facet.core.refs
  • org.eclipse.common.project.facet.core.xml

Will commiting them help my team members or will it mess with their workspace?

What is the best practice approach to this?

解决方案

Generally speaking, you should check-in (and commit after changes) everything that does contribute to the build AND is not re-generateable by re-building completely AND is workstation-specific. (The implications of this statement depend on your build process/procedure, which is intended.)

This implies you should exclude everything that is re-generated upon full build etc. so it is not checked in (and not offered for check-in).

这篇关于我应该提交由eclipse更改的文件的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆