Flex 构建的推荐项目结构
我正在开始一个新项目，使用 Flex3 来实现相当复杂的 UI，从 RESTful Web 服务集合中获取数据。 我想知道其他人在构建中等复杂的 Flex 项目方面有什么经验。 我正在考虑的问题包括：
- 我想使用我们的 FlexBuilder 许可证在 Eclipse
- 自动化构建脚本上进行布局的可视化编辑和调试代码，以便我们可以使用 CI 服务器
- 自动化单元测试
- 测试策略，特别是跨平台 Linux 和 Windows 的 开发环境（是的，我知道 Linux 版本的 FlexBuilder 不进行可视化编辑，但其他一切都应该理想地跨平台运行）
- 对 Java 代码进行依赖管理（有 Flex 的库依赖管理器吗？）
至少 刚刚花了一天的时间尝试但未能让 maven2/flex/jetty 构建设置顺利运行（基于 Jeff Maury 的教程）。 在我们前进的过程中，我并不完全反对使用 Maven，但我确信一定有一条不那么痛苦的路线。 我遇到的主要问题（除了 Maven 文档不完整之外）是 Maven 的“每个构建单个工件”规则意味着您必须通过复杂的构建跳过很多环节，而且我还没有足够的 Maven 启动能力被铁圈绊倒，摔到我脸上！
Ant 和 Ivy 会比 maven2 更好吗？ 还有哪些其他选择？
I'm starting a new project using Flex3 for a reasonably intricate UI getting its data from a collection of RESTful web services. I wondering what experiences others have had in structuring a moderately complex Flex project. The issues I'm thinking about include:
- I want to use our FlexBuilder licenses for visual editing of layouts and debugging code on Eclipse
- automated build script so that we can use a CI server
- testing strategies, particularly automatable unit tests
- cross-platform Linux and Windows development environments (yes, I know the Linux version of FlexBuilder doesn't do visual editing, but everything else should ideally run cross-platform)
- dependency management for at least the Java code (are there library dependency managers for Flex?)
I've just burned a day trying and failing to get a maven2/flex/jetty build setup working smoothly (based on Jeff Maury's tutorial). I'm not dead-against using Maven as we go forwards, but I'm sure there must be a less painful route. The main issue I had (other than maven documentation being patchy) is that maven's "single artifact per build" rule means that you have to jump through a lot of hoops with a complex build, and I'm not enough of a maven initiate not to trip over the hoops and fall on my face!
Would Ant and Ivy be a better option than maven2? What other choices are there?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我不了解Flex开发，但我了解CI，所以我会评论一下这方面。
我在 CruiseControl 上工作，所以这就是我使用的（当没有付费设置其他东西时）。 还有一些博客文章描述了在 CC 下为 Windows 和 Linux。 CC 已经存在很长时间了，因此有一个庞大的用户社区和大量 3rd与之配合使用的派对工具。
但其他人可能会推荐 Hudson 并且很难反驳他们。 Hudson 非常容易启动和运行，并且有一个漂亮的基于 Web 的 UI。 这个项目非常活跃，拥有大量粉丝和热议，并且成熟得非常快。 我对此没有什么不好可说的。 此博客条目描述了 在 Hudson 下运行验收测试。
我对 Maven 的了解还不够，无法提供建议，但我现在正在与客户的 Ivy 合作，我真的很喜欢它。 我们拥有 Java 和 C++ 代码的组合，并且能够让 Ivy 完成我们需要的工作。
I don't know Flex development but I know CI so I'll comment on that aspect.
I work on CruiseControl, so that's what I use (when not being paid to setup something else). And there are blog entries that describe setting up Flex projects under CC for both Windows and Linux. CC has been around for a long time so there is a large community of users and lots of 3rd party tools that work with it.
But other people are likely to recommend Hudson and it would be hard to argue against them. Hudson is very easy to get up and running and has a nice web based UI. This project is very active, has lots of fans and lots of buzz and has matured very rapidly. I don't have anything bad to say about it. This blog entry describes running acceptance tests under Hudson.
I don't know enough about Maven to offer advice there but I'm working with Ivy at a client right now and I really like it. We've got a combination of Java and C++ code and we're able to get Ivy to do what we need.
好吧，我们正在使用maven。 在许多不同网站的帮助下，我使用 Maven 构建了一个企业应用程序。
这篇来自 adobe 的文章确实很有帮助。
http://www.adobe.com/devnet/flex/articles/fullstack_pt1。 html
http://www.adobe.com/devnet/flex/articles/fullstack_pt2。 html
http://www.adobe.com/devnet/flex/articles/fullstack_pt3。 html
您确实需要一个通用的配置项目，该项目将在 Flex 和 Java 之间共享，并且可能还需要您的 C++ 代码。 本文解释了如何进行所有设置。
不利的一面是，如果您不了解 Maven，那么学习曲线会稍有困难。
Well we are using maven. With some help of a lot of different web sties I have an enterprise application being built using maven.
This article via adobe has really help a lot.
http://www.adobe.com/devnet/flex/articles/fullstack_pt1.html
http://www.adobe.com/devnet/flex/articles/fullstack_pt2.html
http://www.adobe.com/devnet/flex/articles/fullstack_pt3.html
You really need a common configuration project that will be shared between both flex and java, and possibly your c++ code. This article explains how to set that all up.
Down side, if you are not knowledgeable with maven there is a slight learning curve.