从 FlexBuilder 3 过渡到 FlashBuilder 4 ...来来回回
又到了生长痛的时间了。我们的一些东西需要 FlashBuilder 4，有些仍然需要 FlexBuilder 3。两者都安装正常，并且没有项目同时使用这两种 IDE。问题是，当我回去处理 FlexBuilder 3 项目时，它需要永远的构建时间，并且我会收到如下奇怪的错误：
除了在构建过程中的各个点抛出模式对话框，强制用户交互之外，这似乎不会导致任何可识别的问题。但我确实注意到 FB3 中的内存很快就被填满了，而且通常 FB3 开始表现得很奇怪，一旦超过 700MB，最终就会退出。
这只是我们将所有项目纳入 FB4 之前的临时过渡情况，但“临时”可能意味着几周甚至几个月。有人对如何度过这个过渡期有什么建议吗？我可以做些什么来让这两个 IDE 协同工作并正常运行吗？如果做不到这一点，有谁知道“java.lang.String”是什么问题的“原因”？当我在两者之间来回切换时，Eclipse 是否有一个资源包在某处被损坏？
It's growing pains time again. Some of our stuff requires FlashBuilder 4 and some still requires FlexBuilder 3. Both are installed OK, and no projects use both IDEs. The trouble is, when I go back to work on a FlexBuilder 3 project it takes freakin' forever to build and I get weird errors like these:
This doesn't seem to cause any identifiable problems except to throw up a modal dialog at various points in the build process, forcing user interaction. But I do notice that memory fills up fast in FB3 and generally FB3 starts behaving strangely and ultimately quits once it gets up over 700MB.
This is only a temporary bridge situation until we get all projects into FB4, but "temporary" could mean weeks if not months. Does anyone have any advice for how to get through this bridge period? Is there anything I can do to make these two IDEs work and play well together? Failing that, does anyone know what "java.lang.String" is the "reason" for the problem? Does Eclipse have a resource bundle somewhere that is getting corrupted when i go back and forth between the two?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
您在 Flex Builder 3 中需要什么，这意味着您不能只在 Flash Builder 4 中使用该项目？
是否有原因导致您无法将项目移至 Flash Builder 4，但指定要继续使用 Flex 3 SDK？您尝试过并遇到问题吗？
谢谢，
安德鲁
土坯
What do you need in Flex Builder 3 that means you cannot just use the project in Flash Builder 4?
Is there a reason why you can't move your projects to Flash Builder 4, but specify that you want to continue using Flex 3 SDK? Have you tried that and run into issues?
Thanks,
Andrew
Adobe