On 7/30/13 11:35 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote:
>Can you give us odds on how likely that "if ever" is? If it's likely >that Adobe will release this as a fix, I'd be willing to release the >SDK in expectation of that event. If not, I'll keep pushing for a >solution we can create and distribute ourselves. I think either I or Adobe will publish something for Flash Builder 4.7. I'm still waiting to find out how long that will take and how it will get published. Now that the JAR has been tested and known to work, I've removed it from my people.a.o folder since that isn't an allowed deployment method. FlashBuilder 4.6 is another story. Is this really critical? It will be a pain for me to resurrect the source and propose the patch, and even more painful to try to convince folks at Adobe that there is a business justification for getting it published. I know folks are still running 4.6 to try to get Design View to work, but I was hoping they also had 4.7 installed and can create new projects in 4.7. Remember, Adobe has stated that only FB 4.7 supports Apache Flex. So, my current position is that it is time to cut another RC and vote on it. All other issues have been addressed. I'm pretty sure FB 4.7 users will be able to fix their installations sooner rather than later. But it depends on how critical folks think a fix for FB 4.6 is. We also have to consider whether having folks replace a JAR is easy enough for the folks who are new to Flex and most likely to run into this issue. Should we be thinking about a utility that finds FB and updates it? -Alex
