Skip navigation
Currently Being Moderated

FlashBuilder4 eclipse plugin for Eclipse Helios 64 bit version

Jul 19, 2010 2:16 AM

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.startActiv ator(Bundl eContextImpl.java:806)

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

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

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

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

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

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

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

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

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

    at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(Bundl eLoader.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(De faultClass 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(BundleH ost.java:2 32)

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

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

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

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

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

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

    at org.eclipse.core.internal.events.BuildManager.initializeBuilder(Build Manager.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(BuildMan ager.java: 311)

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

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

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

    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.getUserFlashP layerTrust Folder(Unknown Source)

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

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

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

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

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

    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActiv ator(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(Bundl eLoader.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(De faultClass 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.getUserFlashP layerTrust Folder(Unknown Source)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

    at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(Bundl eLoader.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(De faultClass 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(BundleH ost.java:2 32)

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

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

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

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

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

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

    at org.eclipse.core.internal.events.BuildManager.initializeBuilder(Build Manager.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(BuildMan ager.java: 311)

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

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

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

    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(Bundl eLoader.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(De faultClass 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.re sourceChan ged(Unknown Source)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

    at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(Bundl eLoader.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(De faultClass 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(BundleH ost.java:2 32)

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

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

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

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

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

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

    at org.eclipse.core.internal.events.BuildManager.initializeBuilder(Build Manager.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(BuildMan ager.java: 311)

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

    at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.ja va: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.startActiv ator(Bundl eContextImpl.java:806)

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

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

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

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

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

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

    ... 27 more

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

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

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

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

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

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

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

    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActiv ator(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(Bundl eLoader.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(De faultClass Loader.java:107)

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

    ... 40 more

 

~ Saurabh

 
Replies 1 2 3 Previous Next
  • Currently Being Moderated
    Jul 26, 2010 6:28 PM   in reply to SaurabhCheenu

    Hi Saurabh,

     

    Flash Builder 4 is compatible with the 32-bit version of Helios, but not with the 64-bit version.

     

    -Chris

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 31, 2010 6:59 PM   in reply to C. Agruss (Adobe)

    We strongly desire to use the new 64-bit Eclipse Helios JEE platform for our development, and plug the Flash Builder 4 Plug-in into it. Our applicaiton is a large enterprise application with a Java server-side and a Flex client side. We have about 50 engineers and 50 professional service people that use this platform. Our engineers and professional services people work on the entire code at once... switching between two different IDEs is a real pain. We did that originally but then figured out how to get the Flex Builder 3 plug-in installed into our existing Java Enterprise Eclipse IDE and have been much happier since.

     

    We have 100+ projects, 50,000+ files, 2.5 million lines of code, and use over 150 third-party jars. Working in a 32-bit IDE is now too much of a pain point. We've hit the wall on the 32-bit JVM... we allocate 256M to PermGen (just about enough) and 1024M to heap. This is a compromise heap size: its not enough heap: compiling and validating everything is always slow and sometimes it fails or hangs thrashing near out of heap space, but it is also too much: we often get other kinds of OOM errors (native memory, etc) because the heap is too large. The 32-bit address space is just too limited for our IDE needs. Thus, we absolutely need to switch to a 64-bit IDE. In our trials with the 64-bit Helios, we allocate 2048m of heap and full builds builds are about 50% faster, and so far, not a single crash from other OOM conditions. Problem is... the Flash Builder 4 Plug-in will install nicely with no errors or warnings, but does not work (many of its .dlls are 32-bit dlls and it fails because it can't load the native library for BridgeTalk).

     

    When will Adobe release a Flash Builder 4 Plug-in that will work with the 64-bit version of Eclipse Helios? Helios is the 64-bit revolution for Eclipse... every package that is available (classic, Java, JEE, etc) is now available in both a 32-bit and a 64-bit download. Adobe should follow suit.

     

    David Williams over on the eclipse.org forums answered this question with this answer: "In an ideal world, a P2 install [of Flash Builder 4] would automatically pick out the right platform version [32-bit or 64-bit] and you'd work with either one transparently."

     

    http://www.eclipse.org/forums/index.php?t=msg&goto=545212&#msg_545212

     

    Thus, we'd like to officially like to request this feature. Is this the proper place ot make a feature request?

     

    -J.C.

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 1, 2010 5:45 AM   in reply to SaurabhCheenu

    I think this is a use case that will see more and more demand as time goes on.

     

    Has Adobe done any kind of LOE estimation on supporting 64 bit eclipse?

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 2, 2010 2:31 PM   in reply to J.C.Hamlin

    Hi,

     

    We are currently monitoring demand for 64bit support for Flash Builder, but do not have any information to share about availability at this time.

     

    For the time being you will need to install and run Flash Builder in a 32bit version of Eclipse.

     

    Thanks,

     

    Andrew Shorten,

    Product Manager, Flash Builder

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 14, 2010 4:33 AM   in reply to Andrew Shorten

    How do you monitor the demand?

     

    The company i'm working at atm, has 20 developers. about 10 made the step to 64 bit, and most of them hate not being able to use fb4 in 64 bit mode.

    Only 2 of the 10, are now using windows 7 with eclipse 32b + fb4. The other 8 are using intellij. IntelliJ support for flex is pretty good, and free. Ofcause you'll have to pay for intellij, but the cost is about the same. Since most Java programmers i know think intelliJ is the better IDE anyway, and intelliJ does provide 64 binaries... it's not even a losing battle, adobe just doesn't have 64 bit flash builder.

     

    I do need an ide with support for flex, i have an intelliJ license. I spend over 1 day to make a big maven project work in eclipse, and now i find out i cannot move on because i used the 64 bit version of eclipse. Sorry adobe, i love eclipse, i love 64 bit, i like flashbuilder, but i guess the others are right, IntelliJ is the way to go atm.

     

    I will not uninstall my 64 bit eclipse, perhaps you guys will have a 64bit fb4 before i get used to intellij.

     

    Please be quick about releasing a 64 bit version.

    I really hope it's going to be today!

     

     

    Daniel

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 22, 2010 2:30 PM   in reply to SaurabhCheenu

    +1 for 64 bit eclipse support...

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 16, 2010 4:36 PM   in reply to SaurabhCheenu

    I'm also awaiting the 64bit plugin...

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 21, 2010 7:21 AM   in reply to SaurabhCheenu

    +1

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 27, 2010 5:58 AM   in reply to SaurabhCheenu

    +1

     
    |
    Mark as:
  • Currently Being Moderated
    Calculating status...
    Nov 1, 2010 3:31 AM   in reply to SaurabhCheenu

    Count my feedback and vote for 64-bit plugin. Windows 7 and 64-Bit Plugins seem to be more mainstream these days

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 5, 2010 11:47 AM   in reply to bobbyworld

    It's good to have choices: "run two IDEs or run a 32 bit Java".  When my kids were young, I liked to give them choices too.  Like "you can eat your lima beans and liver now, or you can go to bed".  Somehow having two bad choices didn't make them happy either.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 11, 2010 8:53 AM   in reply to SaurabhCheenu

    Another vote for 64 bit FB4 here.

    +1

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 11, 2010 8:54 AM   in reply to SaurabhCheenu

    +1 given that 64-bit developer/designer environments are becoming the norm now-a-days.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 11, 2010 8:58 AM   in reply to SaurabhCheenu

    +1 for the FB4 64 bit...

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 11, 2010 9:00 AM   in reply to SaurabhCheenu

    A 64-bit Flash Player is on the way. How about a development environment to go with it? Make my system happy.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 11, 2010 9:02 AM   in reply to SaurabhCheenu

    +1 vote for Flash Builder 4 64-bit.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 11, 2010 9:02 AM   in reply to SaurabhCheenu

    +1 for the FB4 64 bit...

     

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 11, 2010 9:04 AM   in reply to mjondrejko

    +1 for the FB4 64 bit.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 11, 2010 9:07 AM   in reply to SaurabhCheenu

    +1 vote for 64bit Support.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 11, 2010 9:37 AM   in reply to SaurabhCheenu

    +1 provide a 64-bit version of Flash Builder 4.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 11, 2010 9:38 AM   in reply to SaurabhCheenu

    +1 vote for 64bit Support.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 11, 2010 9:50 AM   in reply to J.C.Hamlin

    For a number of reasons very similar to those laid out by J.C.Hamlin, our team is finding that FB4 is the only obstacle to moving to Eclipse 64-bit. This is not only disappointing, we're also missing out on better productivity.

     

    Our organization would very much like to add our vote for this FB4 64-bit version to be made available by Adobe. The sooner the better!

    Thanks.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 11, 2010 11:20 AM   in reply to SaurabhCheenu

    +1 vote for 64bit Support.

     

     

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 11, 2010 12:32 PM   in reply to SaurabhCheenu

    +1

     

    provide a 64-bit version of Flash Builder 4.
     
    |
    Mark as:
  • Currently Being Moderated
    Nov 11, 2010 1:32 PM   in reply to Andrew Shorten

    +1 64-bit

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 11, 2010 8:37 PM   in reply to SaurabhCheenu

    +1 for 64 bit

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 12, 2010 1:18 PM   in reply to SaurabhCheenu

    We need 64bit for sure.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 12, 2010 1:34 PM   in reply to SaurabhCheenu

    +1 for 64 bit

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 12, 2010 9:51 PM   in reply to SaurabhCheenu

    +1 for 64bit Flash Builder.

     

    If you have some feature request page open for this topic as well, please point us to it so we can vote there as well.

     

    Don't see the point in monitoring demand at this point anymore since the demand is clearly there and will only get stronger for each new 64bit computer sold. Computer systems are not going to go back to 32bit. More likely, we'll see 128bit or something in the future.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 13, 2010 6:38 AM   in reply to SaurabhCheenu

    +1 vote for 64bit Support  !!!!

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 14, 2010 10:46 PM   in reply to SaurabhCheenu

    +1 for 64 bit support

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 15, 2010 8:20 AM   in reply to SaurabhCheenu

    +1 for 64-Bit Support

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 15, 2010 9:52 AM   in reply to amarseelam

    Hi,

     

    If you are adding your support for a 64bit version of Flash Builder it would really help if you could provide some context as to why you need it - is it because of a specific issue you are currently facing in Flash Builder, is due to compatibility with other plug-ins you're running or something else?

     

    Thanks,

     

    Andrew

    Group Product Manager, Developer Tools, Adobe

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 15, 2010 10:31 AM   in reply to SaurabhCheenu

    Well, I would echo what J.C. Hamlin wrote (far above).

     

    We've got a very large project with a large java component as well as many flex projects.  Developing in one IDE is VERY convenient in that code refactoring, searching, deployment to the test environment, etc. is all integrated into one IDE instance.  HOWEVER, in our environment, the heap/memory limitations of a 32-bit JVM constrain the performance of eclipse with our projects and all the plugins that we use.

     

    We're constantly trying to balance heap, maxperm, etc. to tune, but we're totally crunched down by the 32-bit JVM 2g limit, and even below that because of Windows overhead and whatever eclipse itself is doing.  When you get it wrong, sometimes eclipse will simply just die, and restoring the workspace to its former state is not always easy and quick.

     

    Even more concerning is that our product as well as eclipse and our other plugin tools (including flashbuilder) is a long-lived one and continues to grow.  Looking down the road, therefore, heap space will continue to be more and more of a limitation.

     

    Our entire development department and many others' that I've talked with use 64-bit OS versions to allow application development with fewer memory constraints.  Eclipse 64-bit works great unless you must have a 32-bit-only plugin.  MyEclipse 9 now supports 64-bit on Windows.

     

    Having flashbuilder as a 64-bit compatible plugin would not only help address this case, but also put you in line with where I would imagine the future of operating systems are eventually heading.  Maybe it will take a few years, but how long before 32-bit apps are as obsolete as 16-bit ones?

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 15, 2010 10:40 AM   in reply to Andrew Shorten

    Ok - why do I want it?

     

    I use Springsource Toolsuite as my base eclipse.  STS includes a nice bit of productivity software called Roo. Roo has a plugin that generates applications with Flex Client and Java back end using BlazeDS in between.  I use the Flashbuilder plugin to work on the client side.  I upgraded to the 64 bit STS, and as they say, "BOOM goes the dynamite".

     

    So no 64 bit Flashbuilder => No Flex Roo plugin => No Roo => No STS in 64bis  => A bit of frustration.

     

    No,  I can not separate the Flex Client and run it in 32 bit Flashbuilder because the Roo plugin manages bidirectional code generation from database to the server side to the Flex client code within the scope of a single project.

     

    Yes I could run a 32 bit STS, but I just got a nice new machine with LOTS of RAM and I swallowed hard and bought yet another copy of Windows. I'd kinda like to make use of it.

     

    This approach of asking "let's examine your motives" in the face of some pretty clear demand from customers may be instructive for you, but it also gives the distinct impression that customers and vendor are not seeing eye-to-eye on the issue. This worries me.  Why is Adobe pushing back on this?

     

    Ted

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 15, 2010 10:41 AM   in reply to Hamilton, Scott J

    The need is simple,

     

    We are running our production environment on a 64bit machine with 64bit os (red hat i beleave), and 64bit JRE.

     

    So to get as close to the same specs, i use a 64bit OS (W7) and 64bit JDK. Next step should be 64bit Eclipse....

     

    So, we cannot run 64bit eclipse because there is no flex support on 64bit eclipse. Going to 32bit eclipse means going to 32bit jre....

     

    it's just to bad....

     

    I guess it's just not a high priority for Adobe, and i might even agree.... to bad that my current project doesn't work with intellij. My last project worked perfect with intellij. IntelliJ support for flex is very good.

     

    I still like Eclipse better. FYI Currently running 32bit jdk with 32bit eclipse with FB4.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 15, 2010 10:42 AM   in reply to Andrew Shorten

    Andrew,

     

    I think I've stated *our* reasons in a message earlier. Due to the size of our codebase and number of projects and third-party libraries, the Helios 32-bit version just simple can't import, compile, and function properly. We run out of memory (either heap space if heap is too small, or out of some other native memory resource if heap is too large). When Eclipse crashes like this, sometimes getting interrupted to get your workspace back into a usable state can be a real pain.

     

    We want to use an *integrated* development environment (the key word being integrated) which means running Helios 64-bit for all of our work (Java, JSP, Database, etc) AND Flex development. Without the integration (i.e. being forced to run two IDEs 32-bit Flash Builder 4 for Flex and 64-bit Helios for Java/JSP) refactoring, search, search and replace, SVN commit/update, deployment and testing, just becomes a pain. So, until Flash Builder 4 comes as a plug-in that plugs into our 64-bit Helios enviornment, we're forced to run two IDEs and have a non-integrated development environment. This is a real pain.

     

    I'm guessing this will be the primary concern you will hear expressed here.

     

    Eclipse is wonderful, but its also a memory hog, and Helios is even moreso than ever (i.e. our project used to work, barely, in 3.4. It sort-of worked in 3.5. It does not work in Heloios [3.6] because we can't even allocate a heap large enough). Helios provides even more features than ever, it also needs more memory to function. This problem will continue to get worse over time so that even smaller projects than ours start to bump into the 32-bit/2G limit.

     

    -J.C.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 15, 2010 12:00 PM   in reply to J.C.Hamlin

    I'll add that it's a bit awkward to have your only paid Eclipse plug-in be the only plug-in that holds you back. With FB3 it held us to Ganymede, and now with FB4 it's holding us to 32 bit. Eclipse users are accustomed to (spoiled by?) short waits between minor updates in plug-in software and not having to wait months (years?) for compatibility updates. I realize that FB is a very sophisticated piece of software, but it is frustrating to see Subversive, m2eclipse, Hibernate Tools, Freemarker IDE, etc. handle version upgrades with no problem while FB chokes.

     

    Note that FB doesn't necessarily need to be optimized for 64 bit...it just needs to survive.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 17, 2010 6:48 AM   in reply to Andrew Shorten

    +1 for the FB4 64-bit

     
    |
    Mark as:
1 2 3 Previous Next
Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points