哪些文件应进入 Flex Builder 项目中的源代码管理？
我注意到 Eclipse (Flex Builder) 生成了数百个元数据文件。 我应该将它们签入我的源代码管理吗？ 它们似乎是必要的，因为如果我删除它们，Flex Builder 只会打开一个空的工作台...
其中一些文件显然不属于源代码管理（例如 .history 文件和一些缓存文件）。 如果我删除它们，我的项目将再次顺利打开。 但该列表很长，并且包含属于源代码管理的文件和不属于源代码管理的文件的文件夹之间似乎没有明确的区别。
即使我要忽略效率低下，我也不能将它们全部推入 svn，因为 Eclipse 会不断生成具有不同名称的新文件，这反过来似乎对于项目的加载也至关重要。
有人可以启发我吗？
I noticed that Eclipse (Flex Builder) generates hundreds of metadata files. Should I check them into my source control? They seem necessary, because if I delete them Flex Builder just opens up an empty workbench...
Some of these files plainly do not belong in source control (like .history files and some cache files). If I delete them my project opens up again without a hitch. But the list is long and there seem to be no clear separation between folders that contain files that belong in source control and those that do not.
I can't just shove them all into svn, even if I were to ignore the inefficiency, because Eclipse generates new ones constantly, with different names, which in turn also seem to be crucial for the project to load.
Can someone please enlighten me?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
不要签入数百个元数据文件。 如果您希望能够以只需导入的方式签出项目，请签入：
以及“html-template”和“libs”。 正如克里斯蒂安所说，你依赖的任何资源。 不过，我通常将它们保留为单独的 Flex 库项目。
Don't check in the hundreds of metadata files. If you want to be able to check out the project in a way that it can just be imported, then check in:
And "html-template" and "libs". As Christian says, any resources you depend on. I usually keep those as separate Flex Library projects though.
我通常将所有源代码放在 src 下，然后检查 src 及其所有后代。 如果我的项目依赖于任何外部依赖项（例如，Cairngorm SWC、as3corelib 等）、Flash/图形资源、样式表或资源文件，我也会将它们签入。 但我不会检查任何生成的 (bin-*)、中间体或 IDE 特定的东西，因为将这些东西放在源代码管理中似乎并没有提供太多实际的好处，而且根据我的经验，这只会让我头疼； 一般来说，我会检查我需要的最少的集合 - 给定一个干净的 FlexBuilder 安装（或者根本没有安装 - 例如，如果我使用 mxmlc 或 compc 进行编译）和一个空项目 - 以成功构建项目。
I generally put all of my source code under src, and I check in src and all of its descendents. If my project relies on any external dependencies (e.g., the Cairngorm SWC, as3corelib, etc.), Flash/graphical assets, stylesheets, or resource files, I check those in, too. But I don't check in any generated (bin-*), intermediate or IDE-specific stuff, because having that stuff in source control doesn't seem to provide much practical benefit, and in my experience has only caused me headaches; in general, I check in the most minimal set of whatever I'd need -- given a clean FlexBuilder installation (or none at all -- for example, if I were compiling instead with mxmlc or compc) and an empty project -- to build the project successfully.
大多数 Eclipse 项目文件，如 .project、.properties、.settings 中的所有内容，都可以进入源代码管理。 只要文件没有依赖于用户的设置（例如文件路径或本地 URL），就应该没问题。
我们使用的一种方法是创建不在 SCM 中使用但包含在 SCM 中的本地属性文件。 IE 是一个 ant 构建文件，包括具有本地元数据的 local.properties 文件。
Most of the eclipse project files, like .project, .properties, everything in .settings, can go into your source control. As long as the files don't have user-dependent settings like file paths or local urls, you should be fine.
One method we use is creating local property files that don't get used in SCM, but are included in the ones that do. I.E an ant build file including a local.properties file which has local metadata.
如果 .actionScriptProperties、.project 或 .flexProperties 中有与用户相关的内容怎么办？ 通常，这将是 url 或路径信息。 外部化这个的最佳实践方法是什么？ 我尝试创建路径变量，但这显然只适用于路径。 不适用于主机名等内容。
What if the .actionScriptProperties, .project, or .flexProperties have user-dependent stuff in them? Typically this will be url or path information. What's the best practice way of externalizing this? I tried creating path variables, but this only works obviously for paths. Not for things like hostname, etc.