将eclipse工作空间提交到版本控制时应该忽略哪些目录/文件? [英] What directories/files should be ignored when commiting eclipse workspaces to version control?
问题描述
我是Eclipse新手,我有一个Eclipse工作区,其中包含Google Web Toolkit应用程序的项目。什么目录/文件应该提交到版本控制(我们使用Subversion)?我相信我不需要提交.metadata目录,在我看来,我不需要提交战争目录,但我不是积极的。承诺的项目需要跨多个开发人员共享。
I'm an Eclipse newbie, and I have an Eclipse workspace with projects for a Google Web Toolkit App. What directories/files should I commit to version control (we're using Subversion)? I believe I don't need to commit .metadata directories, and it seems to me that I don't need to commit war directories, but I'm not positive. The committed projects need to be shared across multiple developers.
推荐答案
stacker 涵盖了Eclipse的文件,让我来看GWT;)
stacker covered Eclipse's files, let me cover GWT ;)
假设您使用的是标准布局:
war目录是您的Web应用程序的部署
映像。标准扩展战争格式
是
,由各种Java Web
服务器识别,包括Tomcat,Jetty和
其他J2EE servlet容器。
包含各种资源:
The war directory is the deployment image of your web application. It is in the standard expanded war format recognized by a variety of Java web servers, including Tomcat, Jetty, and other J2EE servlet containers. It contains a variety of resources:
- 您提供的静态内容,如主机HTML页面
- GWT编译输出
- 服务器端代码的Java类文件和jar文件
- 配置Web的web.xml文件应用程序和任何servlets
- Static content you provide, such as the host HTML page
- GWT compiled output
- Java class files and jar files for server-side code
- A web.xml file that configures your web app and any servlets
所以你可以看到它是一个混合的包。由于之前建议,您应该使用 svn:ignore
让SVN知道你想在源代码控制下放置什么 - 显然,编译的输出和类文件是:)
So as you can see it's a mixed bag. As it's been suggested before, you should use svn:ignore
to let SVN know what exactly you want to put under source control - obviously the compiled output and class files are out :)
这篇关于将eclipse工作空间提交到版本控制时应该忽略哪些目录/文件?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!