将 Flex3 项目置于源代码控制（颠覆）之下的最佳方法是什么
为小组开发设置 Flex 项目可能有点棘手。 为了使项目可以轻松签出，可能需要调整许多小的本地设置。
我使用内置的导入/导出 Flex 项目实用程序取得的成功有限。 我似乎经常手工编辑，我想我可能会遗漏一些东西。
更新 我最初忽略了提及，我的目标是使从颠覆中签出项目并尽可能少地启动和运行成为可能。 我遇到的最大问题都围绕着管理“点”文件以及如何使它们足够灵活以处理不同的开发人员环境。
例如，即使只有我一个人，我也希望拥有这样的能力：在工作中我使用 Vista 机器，在家里我使用 Mac。 某些路径的描述方式当然存在差异，但它们确实非常相似。 在 Vista 上，flex 根目录是 c:/ColdFusion8/wwwroot，在 OS X 上，它是 /Applications/ColdFusion8。 我已经能够为 CF_FLEX_SERVER 和 WEBSERVER 设置链接资源路径变量，然后使用 ${WEBSERVER}/myProject 语法引用该变量。
到目前为止，它似乎运行得很好，但我发现它仍然有一些问题。 具体来说，在 .project 文件中，您会发现类似以下内容：
<linkedResources>
<link>
<name>bin-debug</name>
<type>2</type>
<location>c:/inetpub/wwwroot/myProject-debug</location>
</link>
</linkedResources>
不幸的是，如果我尝试将位置实体更改为 ${WEBSERVER}/wwwroot/myProject-debug，flex 会引发编译器错误。 这很遗憾，因为几乎其他一切都有效。
Setting up Flex project for group development can be a bit tricky. There are lots of little local settings that might need to be tweaked in order to have a project that can be easily checked out.
I've had limited success using the built-in import/export flex project utilities. I seem to wind up editing by hand a lot and I think I might be missing something.
UPDATE
I neglected to mention originally that my goal is to make it possible to checkout a project from subversion and get up and running with as little fuss as possible. The biggest problems that I have run into all revolve around managing the "dot" files and how to make them flexible enough to deal with different developer environments.
For example, even with just me, I would like to have this ability: at work, I use a Vista machine and at home I use a Mac. There are certainly differences in the way certain paths are described, but they really are quite similar. On Vista, the flex root is c:/ColdFusion8/wwwroot, on OS X, it is /Applications/ColdFusion8. I have been able to set up a linked resource path variable for both CF_FLEX_SERVER and WEBSERVER that I then reference using the ${WEBSERVER}/myProject syntax.
So far, it seems to work pretty well, but I find there are a few places that it still has issues. Specifically, in the .project file you find something like:
<linkedResources>
<link>
<name>bin-debug</name>
<type>2</type>
<location>c:/inetpub/wwwroot/myProject-debug</location>
</link>
</linkedResources>
Unfortunately, if I try to change the location entity to ${WEBSERVER}/wwwroot/myProject-debug, flex throws a compiler error. That's a shame, because pretty much everything else works.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我之前已经解决过这个问题，并且通常将我的项目设置为这样：
我确实将我的项目（.actionScriptProperties、.flexProperties、.project、.settings）保留在 SVN 中，但不是我的工作区（.metadata），因为它太大了。
我发现通过 Import -> 导入项目 Flex Project 实施了很多限制。 例如，如果您的工作区位于上面的“trunk”目录中，那么作为 Flex 项目导入将导致项目被复制到 trunk/Application 中，或者只是抱怨该位置。
更好的方法是创建工作区，然后导入 -> [常规] 将现有项目放入工作区。 唯一的区别是您必须手动添加 Flex Development 透视图。
编辑：我还建议将编译器选项设置为“使用默认 SDK”，然后将适当的 SDK 设置为默认值。 当每个开发人员为其 SDK 命名不同时，这将阻止提交网球。
I have worked through this problem before and generally set my projects up as such:
I DO keep my project (.actionScriptProperties, .flexProperties, .project, .settings) in SVN, but NOT my workspace (.metadata) because it's too big.
I find that importing projects via Import -> Flex Project enforces alot of restrictions. For example, if your workspace was in the 'trunk' directory above then importing as a Flex Project will cause the project to be copies into trunk/Application or simply complain about the location.
The better way to go about it is to create the workspace and then Import -> [General] Existing Projects into Workspace. The only difference is that you will have to manually add the Flex Development perspective.
Edit: I'd also recommend setting your compiler options to "Use default SDK" and then setting the appropriate SDK as default. This will prevent commit-tennis when each developer names his SDK differently.
由于 Flex Builder 是在 Eclipse 之上编写的，因此它可以与 Subclipse 集成。 这使您可以轻松地将文件标记为“SVN 忽略”以避免特定于项目的设置。 我用它来将我的 Flex 项目添加到现有的 SVN 存储库中，我已将其检出到多个站点。 我注意到这里和那里有一些问题（有些签入会出现错误，但相对罕见），但它通常有效。
Since Flex Builder is written on top of Eclipse, it can integrate with Subclipse. This allows you to pretty easily tag files as 'SVN ignore' to avoid project-specific settings. I've used this to add my Flex projects to an existing SVN repository, which I've checked out to multiple sites. I have noticed a few issues here and there (some checkins get errors, but they're relatively rare), but it generally works.