FlashBuilder4 eclipse plugin for Eclipse Helios 64 bit version

[SaurabhCheenu]

Hello,

I installed FlashBuilder4 trial version which is not a standalone application but rather eclipse plugin, in my latest Eclipse installation which is Eclipse Helios 64 bit version. The installation went on smoothly but after i restarted my Eclipse instance and upon clicking the Flex module from Properties menu it popped up quite a few issues.

I did some research and came to know that Adobe is not supporting 64 bit version of Eclipse.

My question is whether it is a problem or am i missing something. Was anyone able to make the FlashBuilder4 work with Eclipse Helios 64 bit version. If not is there any chance of Adobe releasing the plugin which will work in Eclipse 64 bit. This is rather important for us since we are looking to port our application infrastructure to use 64 bit Eclipse, JVM etc and if Adobe is not supporting that it will become a show stopper for us and we have to fall upon using 2 different IDE(s) as a last resort.

Looking forward to  hear from Adobe people soon with few silver linings!!!!!

Here are my system details:

Windows XP SP2 64 bit professional edition, 8 gb RAM, 2.93 Ghz

I tried to make it work on Eclipse Helios JEE 64 bit version with Adobe FlashBuilder4 trial version.

Here is the stacktrace that i could retrieve from my Eclipse Log file hope this helps:

!ENTRY org.eclipse.osgi 4 0 2010-07-06 00:39:06.330

!MESSAGE An error occurred while automatically activating bundle com.adobe.flexbuilder.project (1075).

!STACK 0

org.osgi.framework.BundleException: Exception in com.adobe.flexbuilder.project.internal.FlexProjectCore.start() of bundle com.adobe.flexbuilder.project.

    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(Bundl eContextImpl.java:806)

    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextI mpl.java:755)

    at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java :370)

    at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.ja va:284)

    at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:417)

    at org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java: 265)

    at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass (EclipseLazyStarter.java:106)

    at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathMa nager.java:453)

    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(Default ClassLoader.java:216)

    at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java: 393)

    at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.ja va:469)

    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:422)

    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:410)

    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClass Loader.java:107)

    at java.lang.ClassLoader.loadClass(ClassLoader.java:248)

    at org.eclipse.osgi.internal.loader.BundleLoader.loadClass(BundleLoader.java:338)

    at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:2 32)

    at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundl e.java:1197)

    at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableEx tension(RegistryStrategyOSGI.java:174)

    at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension( ExtensionRegistry.java:904)

    at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtensi on(ConfigurationElement.java:243)

    at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableE xtension(ConfigurationElementHandle.java:55)

    at org.eclipse.core.internal.events.BuildManager.instantiateBuilder(BuildManager.j ava:784)

    at org.eclipse.core.internal.events.BuildManager.initializeBuilder(BuildManager.ja va:737)

    at org.eclipse.core.internal.events.BuildManager.getBuilder(BuildManager.java:482)

    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:201)

    at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:255)

    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)

    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:258)

    at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java: 311)

    at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:343)

    at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144)

    at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:242)

    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

Caused by: java.lang.NoClassDefFoundError: com/adobe/flexbuilder/utils/osnative/NativeControl

    at com.adobe.flexbuilder.project.internal.PlayerTrustStore.getUserFlashPlayerTrust Folder(Unknown Source)

    at com.adobe.flexbuilder.project.internal.PlayerTrustStore.<init>(Unknown Source)

    at com.adobe.flexbuilder.project.internal.PlayerTrustStore.getInstance(Unknown Source)

    at com.adobe.flexbuilder.project.internal.FlexProjectCore.start(Unknown Source)

    at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextI mpl.java:783)

    at java.security.AccessController.doPrivileged(Native Method)

    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(Bundl eContextImpl.java:774)

    ... 33 more

Caused by: java.lang.ClassNotFoundException: com.adobe.flexbuilder.utils.osnative.NativeControl

    at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.ja va:506)

    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:422)

    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:410)

    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClass Loader.java:107)

    at java.lang.ClassLoader.loadClass(ClassLoader.java:248)

    ... 40 more

Root exception:

java.lang.NoClassDefFoundError: com/adobe/flexbuilder/utils/osnative/NativeControl

    at com.adobe.flexbuilder.project.internal.PlayerTrustStore.getUserFlashPlayerTrust Folder(Unknown Source)

    at com.adobe.flexbuilder.project.internal.PlayerTrustStore.<init>(Unknown Source)

    at com.adobe.flexbuilder.project.internal.PlayerTrustStore.getInstance(Unknown Source)

    at com.adobe.flexbuilder.project.internal.FlexProjectCore.start(Unknown Source)

    at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextI mpl.java:783)

    at java.security.AccessController.doPrivileged(Native Method)

    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(Bundl eContextImpl.java:774)

    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextI mpl.java:755)

    at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java :370)

    at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.ja va:284)

    at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:417)

    at org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java: 265)

    at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass (EclipseLazyStarter.java:106)

    at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathMa nager.java:453)

    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(Default ClassLoader.java:216)

    at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java: 393)

    at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.ja va:469)

    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:422)

    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:410)

    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClass Loader.java:107)

    at java.lang.ClassLoader.loadClass(ClassLoader.java:248)

    at org.eclipse.osgi.internal.loader.BundleLoader.loadClass(BundleLoader.java:338)

    at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:2 32)

    at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundl e.java:1197)

    at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableEx tension(RegistryStrategyOSGI.java:174)

    at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension( ExtensionRegistry.java:904)

    at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtensi on(ConfigurationElement.java:243)

    at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableE xtension(ConfigurationElementHandle.java:55)

    at org.eclipse.core.internal.events.BuildManager.instantiateBuilder(BuildManager.j ava:784)

    at org.eclipse.core.internal.events.BuildManager.initializeBuilder(BuildManager.ja va:737)

    at org.eclipse.core.internal.events.BuildManager.getBuilder(BuildManager.java:482)

    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:201)

    at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:255)

    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)

    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:258)

    at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java: 311)

    at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:343)

    at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144)

    at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:242)

    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

Caused by: java.lang.ClassNotFoundException: com.adobe.flexbuilder.utils.osnative.NativeControl

    at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.ja va:506)

    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:422)

    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:410)

    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClass Loader.java:107)

    at java.lang.ClassLoader.loadClass(ClassLoader.java:248)

    ... 40 more

!ENTRY org.eclipse.core.resources 4 2 2010-07-06 00:39:07.611

!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.resources".

!STACK 0

java.lang.NoClassDefFoundError: com/adobe/flexbuilder/project/internal/ApplicationResourceListener$1

    at com.adobe.flexbuilder.project.internal.ApplicationResourceListener.resourceChan ged(Unknown Source)

    at org.eclipse.core.internal.events.NotificationManager$2.run(NotificationManager. java:291)

    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)

    at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager .java:285)

    at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(Notificat ionManager.java:149)

    at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.jav a:327)

    at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1181)

    at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:157)

    at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:242)

    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

Caused by: org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter$TerminatingClassNo tFoundException: An error occurred while automatically activating bundle com.adobe.flexbuilder.project (1075).

    at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass (EclipseLazyStarter.java:121)

    at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathMa nager.java:453)

    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(Default ClassLoader.java:216)

    at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java: 393)

    at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.ja va:469)

    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:422)

    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:410)

    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClass Loader.java:107)

    at java.lang.ClassLoader.loadClass(ClassLoader.java:248)

    at org.eclipse.osgi.internal.loader.BundleLoader.loadClass(BundleLoader.java:338)

    at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:2 32)

    at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundl e.java:1197)

    at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableEx tension(RegistryStrategyOSGI.java:174)

    at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension( ExtensionRegistry.java:904)

    at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtensi on(ConfigurationElement.java:243)

    at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableE xtension(ConfigurationElementHandle.java:55)

    at org.eclipse.core.internal.events.BuildManager.instantiateBuilder(BuildManager.j ava:784)

    at org.eclipse.core.internal.events.BuildManager.initializeBuilder(BuildManager.ja va:737)

    at org.eclipse.core.internal.events.BuildManager.getBuilder(BuildManager.java:482)

    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:201)

    at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:255)

    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)

    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:258)

    at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java: 311)

    at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:343)

    at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144)

    ... 2 more

Caused by: org.osgi.framework.BundleException: Exception in com.adobe.flexbuilder.project.internal.FlexProjectCore.start() of bundle com.adobe.flexbuilder.project.

    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(Bundl eContextImpl.java:806)

    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextI mpl.java:755)

    at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java :370)

    at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.ja va:284)

    at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:417)

    at org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java: 265)

    at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass (EclipseLazyStarter.java:106)

    ... 27 more

Caused by: java.lang.NoClassDefFoundError: com/adobe/flexbuilder/utils/osnative/NativeControl

    at com.adobe.flexbuilder.project.internal.PlayerTrustStore.getUserFlashPlayerTrust Folder(Unknown Source)

    at com.adobe.flexbuilder.project.internal.PlayerTrustStore.<init>(Unknown Source)

    at com.adobe.flexbuilder.project.internal.PlayerTrustStore.getInstance(Unknown Source)

    at com.adobe.flexbuilder.project.internal.FlexProjectCore.start(Unknown Source)

    at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextI mpl.java:783)

    at java.security.AccessController.doPrivileged(Native Method)

    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(Bundl eContextImpl.java:774)

    ... 33 more

Caused by: java.lang.ClassNotFoundException: com.adobe.flexbuilder.utils.osnative.NativeControl

    at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.ja va:506)

    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:422)

    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:410)

    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClass Loader.java:107)

    at java.lang.ClassLoader.loadClass(ClassLoader.java:248)

    ... 40 more

~ Saurabh

[ashorten_adobe]

Thank you to those providing additional detail about why you're looking for a 64bit version of Flash Builder - the information about the size and complexity of projects (not just for Flex, but also corresponding Java projects, etc) really does help.

Unfortunately, providing a 64bit version of Flash Builder is a more complex than might first appear, due to the number of libraries and components that Flash Builder is dependent upon, both from other teams within Adobe and externally.

We are however working on our plans for future versions of Flash Builder and are tracking the requirement for a 64bit version of the product as a high priority. I am sorry that I can't provide specific information as to when 64bit Eclipse will be supported, but I will follow up on this thread when we can share details. In the meantime, we are continuing to make significant memory and performance improvements for Flash Builder 4.5 (codename "Burrito") and so I hope you will see some improvements in that release.

Thanks,

Andrew Shorten

Group Product Manager, Developer Tools, Adobe

[deyan_none]

Hi Andrew,

we are a company with 10 developers. We have a pretty big project that consists of about 10 library projects and 1 application that depends on them all.

We use mac os. We usually start flash builder ( eclipse ) with -Xmx1536m - as this is the max supported on 32 bit jvm on mac os.

We have to restart flash builder each few hours as it gets extremely slow. We need to be able to start flash builder with more memory, so please do consider 64bit helios based flash builder as a really high priority task !

We are using flex for really big apps, not just small RIA, banners and small stuff like that.

Also: Please do consider Linux version of flash builder ! We were forced to invest in macs only because of flash builder. We don't want to use windows for religious reasons about which i really don't want to argue 

End users might not be using linux, but developers do use linux !

Cheers,

Deyan

[aubryvn]

+1 vote for 64bit Support.

[O_Red]

+1 for 64bit support.

if adobe wants to remain competitive as a player in the digital era we are living in, it needs to do more than just stay current, they need to stay ahead of the times. we need hardware accelleration, we need updates and enhancements to the language, to the IDE, we need it now now now.

[codealien]

+11 Firmly in need of 64bit support - it won't be long before we will be unable to continue building.  Tweaking eclipse.ini and moving to faster work stations can only take us so far.

Adobe must support Large Scale Application development

[Pepe_FxUG]

+1 here

thanks

Shigeru Nakagaki

[FengSun]

i++;

// Thanks!

[HarpoMarx-de]

And one more for 64bit...

+1

[Décider]

+1 vote

PLEAAAAAASE!!!!!!!

[nbilyk]

+1 for 64bit support

[Pepe_FxUG]

Here is Flex JIRA entry.

https://bugs.adobe.com/jira/browse/FB-10052

Let's vote this!!

Shigeru Nakagaki

[ipo30]

+1 for 64bit support.

[kkras]

throw my +1 in the hat too. Argh.

[Guest]

+1 for 64bit support

actually we need it for all our devs in the office so +6!

[Krishna_Kotha]

+1 for 64bit support.

[yif]

Still not enough demand?

+1 for 64bit support.

[Guest]

+ 1 more for 64-bit support

[IWantToLikeAdobe]

+1 for a 64 bit version.

Adobe, seriously not cool.

I mean, come on!

We live in an age of openness.

How can Adobe claim to be competitive/compliant/advanced if it does not join the rest of the world? windows 64 bit is years old now, and so is Java and eclipse.

This is just classic Adobe mentality, and is what's threatening it's downfall, due to the widely agreed supremacy of things like JQuery and HTML5. Not because they are better, but because they adhere to standards, their power is in collaboration with technologies, not from enforcing them!

You can not live in a bubble and still be competitive. You are not stable if you just say you are while blaming your developers and not advanced if others are way past you in conforming to advances in technology.

What I see here are people begging Adobe to let them be their customers, and a bunch of excuses for what should be a non-issue.

People are saying they need the extra kick that 64-but provides, and they get answered that their projects should not be this large, or that they should use less plugins?

if you want to talk to Java, you should speek it's language. That of community, openness, and technological progress.

And don't even get me started on the support for 64-bit linux...

but I guess, to paraphrase google chrome's crash report:

THE FOLLOWING TECHNOLOGY HAS BECOME UNRESPONSIVE: ADOBE FLEX

[crich2784]

+1

[eapostol]

+1 for 64-bit support as well.

[TFowl]

[This is a repost of a comment I posted on the corresponding bug's JIRA entry]

Hi All-

Not to start any sort of inflammatory dialog here, but I've been watching this topic very closely for quite some time now; both here in the forums and abroad on the net and I've realized the lack of 64-bit Eclipse support is simply unrealistic from a software company which claims its products can be used at the enterprise level. To assume that a single 32-bit version of the plugin is sufficient for every customer's needs is naive and narrow-minded. Brian Kotek posted a comment on this issue (2011-03-11) as did others regarding the amount of memory needed to be productive while developing a real-world application and he's right on the money. To add to his sentiment, and I'm fairly certain I'm not alone on this, but I use the plug-in installation of Flash Builder 4/4.5 primarily because rarely, if ever, do I develop on a project where the only technology utilized is Flash/Flex/AIR or combination thereof. Eclipse allows me to use multiple perspectives to conduct development in various technologies in one IDE. This is why 64-bit is really essential, and not because it's the latest and greatest mind you. Running a single IDE to develop in multiple languages/platforms requires a substantial amount of memory. Furthermore, if I am developing an application which includes a server component or if I'm developing a mobile application (potentially and most likely for multiple devices) I'll have some sort of application server running or running multiple device emulators at once, respectively. As a result, developing in N number of technologies/tiers requires considerably more memory, albeit significantly less memory than running multiple IDEs. It seems as if the decision to not support 64-bit may have stemmed from looking at Flash Builder (and how it is used in the wild) in a vacuum or in isolation excluding all the additional applications which may be running on a developer's workstation at any given time. I really hope Adobe understands this and realizes this truly is an essential requirement for its customers, because if they don't I'm afraid it won't be much longer before developers and technology decision-makers realize developing for the enterprise with these so-called enterprise-level applications and their corresponding platforms is also unrealistic.

Best,

Thomas Fowler

[Edited to include the link to the bug in JIRA]

[ashorten_adobe]

Hi,

Thank you for your feedback on this issue.

I can confirm that we understand the requirement for 64 bit support and are working on plans to offer a compatible version of Flash Builder.

Unfortunately I cannot provide a date for availability at this stage. We'll provide more details in due course.

Thanks,

Andrew Shorten

Group Product Manager, Adobe

[IWantToLikeAdobe]

Hi Andrew,

Thank you for that.

Might I add that 64 bit support is now even more important then ever with

Flex becoming a more valid mobile player. We need to provide at least 256MB

for a mobile emulator of choice.

Also, FDT provides 64 bit support since version 4.2 released in Febuary.

This alone should explain the need for Adobe to catch up.

I like the 4.5 trial I got, I think it's a kick-butt software, but the

productivity and comfort

issues stated herein will take there toll on your customer base.

Thanx again.

[TFowl]

Hi Andrew-

Thanks for the prompt reply to my comment; it is greatly appreciated. It is definitely encouraging to know a 64-bit version is, at the very least, on the horizon. Again, I hope my comments were not taken to be inflammatory or overly critical. My intention was merely to convey that this is becoming more of an issue and a pain point for developers who are investing resources in and committing to the Flash Platform, as a whole. As long as there is some relief in sight for this issue in the near future, I'm sure a lot of folks will be much more at ease going forward. Thanks again for your response and best of luck to you and your team with the 64-bit release.

Sincerely,

Thomas Fowler

[david_kenneth_coleman]

Hi Andrew,

I hope you realize that you are facing a VERY frustrated community here.

We NEED a 64 bit version.  It's been 4 months since your promise to "provide more details in due course."  I think the course is due.

Now with the release of Eclipse Indigo, Flash Builder is again lagging behind a version plus being restricted to a legacy operating mode.

HTML 5 is not a threat in my mind since flex has critical advantages... but in terms of product support...  Major industry level FAIL!!!

Developers are begging you guys for this, we are the reason for your success, please respond to us!

Sincerely,

David K. Coleman