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

[santoshKumar1111111]

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

[daniel_yang1]

+1 vote for 64bit Support.

[ajdavuluri]

+1 vote for 64bit Support.

[Stephen_Kirchner]

+1

provide a 64-bit version of Flash Builder 4.

[susmithajacob]

+1 for 64 bit

[x3xxx]

We need 64bit for sure.

[flash_64]

+1 for 64 bit

[Jens_Wegar]

+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.

[cloverfish71]

+1 vote for 64bit Support  !!!!

[Guest]

+1 for 64 bit support

[amarseelam]

+1 for 64-Bit Support

[ashorten_adobe]

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

[Ted_Moens]

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

[J_C_Hamlin]

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.

[srstclair]

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.

[Hamilton__Scott_J]

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?

[Guest]

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.

[MarcPP]

+1 Need 64bit support yesterday

[nikos101]

Adobe, what are the issues in making fb4 64 bit from 32?

[nikos101]

Just out of interest, I do php, java and flex. Do you reccomend getting a bare bones Helios and then installing the Java,PDT stuff from the main update site? Then install FB4 plugin.

[Guest]

+1 64bit.

[Ted_Moens]

Why do we need a 64 bit plugin?

I've been using the 32 bit plugin on a 32 bit machine with a 32 bit Springsource Toolsuite as my Eclipse IDE.

On my new 64 bit setup, Adobe forced me to run my 64 bit Springsource Toolsuite version of Eclipse spearate from the 32 bit standalone FlexBuilder.  Turns out I want to edit a few simple XML and HTML files in my Flex project.  Surprise - Flexbuilder grants me a plain old text editor to do it with!  Well, ok, how hard can it be to go get an XML editor plugin into Flexbuilder? It's Eclipse after all.

So, I try to get the XML editor from http://download.eclipse.org/releases/helios=> Web, XML, Java EE Devlopment Tools=> Eclipse XML Editors and Tools.  Surprise! (See Below.) Dealing with this is just too far away from any productive work.  What I'd like is a 64 bit plugin that I can stick back in my 64 bit STS and get on with my work.

Cannot complete the install because of a conflicting dependency.
  Software being installed: Eclipse XML Editors and Tools 3.2.2.v201008170029-7H7AFUQDxumQGOpBqffOY2f1qxDZ (org.eclipse.wst.xml_ui.feature.feature.group 3.2.2.v201008170029-7H7AFUQDxumQGOpBqffOY2f1qxDZ)
  Software currently installed: Adobe Flash Builder 4.0.1 (com.adobe.flexbuilder.standalone.product 4.0.1)
  Only one of the following can be installed at once:
    Eclipse Jobs Mechanism 3.4.100.v20090429-1800 (org.eclipse.core.jobs 3.4.100.v20090429-1800)
    Eclipse Jobs Mechanism 3.5.0.v20100515 (org.eclipse.core.jobs 3.5.0.v20100515)
    Eclipse Jobs Mechanism 3.5.1.R36x_v20100824 (org.eclipse.core.jobs 3.5.1.R36x_v20100824)
  Cannot satisfy dependency:
    From: Adobe Flash Builder 4.0.1 (com.adobe.flexbuilder.standalone.product 4.0.1)
    To: org.eclipse.rcp.feature.group [3.5.1.R35x_v20090811-9SA0FxVFqE70OL1ARMrfcO6e7BA6]
  Cannot satisfy dependency:
    From: Eclipse RCP 3.5.1.R35x_v20090811-9SA0FxVFqE70OL1ARMrfcO6e7BA6 (org.eclipse.rcp.feature.group 3.5.1.R35x_v20090811-9SA0FxVFqE70OL1ARMrfcO6e7BA6)
    To: org.eclipse.core.jobs [3.4.100.v20090429-1800]
  Cannot satisfy dependency:
    From: Structured Source Model 1.1.502.v201008311901 (org.eclipse.wst.sse.core 1.1.502.v201008311901)
    To: bundle org.eclipse.core.jobs [3.5.0,4.0.0)
  Cannot satisfy dependency:
    From: WST XML Core 3.2.2.v201008170029-7C7OFXYF7RZHQHI5PyJwPT (org.eclipse.wst.xml_core.feature.feature.group 3.2.2.v201008170029-7C7OFXYF7RZHQHI5PyJwPT)
    To: org.eclipse.wst.sse.core [1.1.502.v201008311901]
  Cannot satisfy dependency:
    From: Eclipse XML Editors and Tools 3.2.2.v201008170029-7H7AFUQDxumQGOpBqffOY2f1qxDZ (org.eclipse.wst.xml_ui.feature.feature.group 3.2.2.v201008170029-7H7AFUQDxumQGOpBqffOY2f1qxDZ)
    To: org.eclipse.wst.xml_core.feature.feature.group [3.2.2.v201008170029-7C7OFXYF7RZHQHI5PyJwPT]

Cannot satisfy ... customers?

[GazonkFoo]

A 64bit version of the plugin is a major demand for our company.

I'm currently facing huge issues when working with the 32bit version of eclipse and flash builder.

My workspace holds 137 projects and is constantly growing and i'm experiencing a steady increase in crashes related to memory issues.

We are currently in the evaluation process for a flash builder replacement because of this.

[ashorten_adobe]

Hi,

Thanks for providing some context around why you need a 64 bit version.

I'm interested to understand why you're working with 137 projects in a workspace - are all of these related to a single application that you're working on, or are you working on a number of discrete applications at any one point in time? Can you provide an estimation as to the number of files contained within those projects and also the total number of lines of code (MXML/AS)?

If you'd prefer to provide more context off-list then please email me: shorten at adobe.com.

Thanks again for your help.

Andrew Shorten,

Group Product Manager, Developer Tools, Adobe

[GazonkFoo]

Hello Andrew,

We are building a larger scale portal-like enterprise application.

My workspace is entirely dedicated to this project and consists of java(-ee) as well as flex projects.

A quick survey revealed the following numbers:

~500 .mxml files having ~35000 LOC

~1600 .as files -> ~140000 LOC

~5000 .java files -> ~450000 LOC

Total # files: ~17000 (this includes resources, eclipse files, build scripts etc)

Those numbers do not contain any third party libs/classes or flex sdk files.

I'm currently running eclipse using -Xmx768M -Xss128K -XX:MaxPermSize=128M
If i increase the maximum heap, i'm facing errors like "java.lang.OutOfMemoryError: unable to create new native thread".

My current setup allows me to work around half a day without an eclipse crash.

Thanks for your help.