On 7/30/13 12:09 PM, "OmPrakash Muppirala" <bigosma...@gmail.com> wrote:
>Thanks for digging into this issue and finding a solution. >My thoughts/concerns on this: > > - It is really up to Adobe to figure out if they want to honor their > user base's desire to continue using FB 4.6. DV does not work with >Apache > Flex in any case. > - Will the fix for FB 4.7 work with future releases of Apache Flex > (4.11, 5.0.0, 5.0.5, etc.) ? Is this something we can easily test >today? I bumped the upper limit from 5 to 100. I figure if we get to version 100 in Apache Flex we'll either be so popular that Adobe will be interested in cranking out new releases of FB, or FB will have been left behind by the community in favor of some other tool vendors. In theory you can test by editing flex-sdk-description.xml > - Any chance the fix be released as a patch to FB 4.7 instead of you > having to host the .jar file somewhere? Maintaining a tool for this >would > be too cumbersome. I'm waiting to find that out, but I'd say the odds are slim. Naturally, the less work we want it to be for our customers, the more work Adobe has to do. I think the options are things like: 1) Adobe creates new binaries for FB 4.7 and Adobe Auto Updater pushes the fix 2) Adobe releases some tool that updates your FB 4.7 installation. 3) Adobe posts the patched JAR on some FB page on www.adobe.com with instructions 4) Adobe gives me permission to post the JAR on my blog. There are other factors like how much testing and support Adobe will commit to. I honestly don't know where we'll end up. -Alex > >Thanks, >Om > > >On Tue, Jul 30, 2013 at 11:54 AM, Alex Harui <aha...@adobe.com> wrote: > >> >> >> 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 >> >>
