Skip navigation

FlashBuilder4 eclipse plugin for Eclipse Helios 64 bit version

Jul 19, 2010 2:16 AM

  Latest reply: yosrabaccar, Mar 6, 2013 8:26 AM
Replies 1 2 3 Previous Next
  • Currently Being Moderated
    Nov 18, 2010 1:45 PM   in reply to SaurabhCheenu

    +1 Need 64bit support yesterday

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 19, 2010 4:24 AM   in reply to MarcPP

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


     
    |
    Mark as:
  • Currently Being Moderated
    Nov 19, 2010 4:30 AM   in reply to nikos101-gYzbwT

    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.

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

    +1 64bit.

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

    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?

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 30, 2010 12:47 AM   in reply to SaurabhCheenu

    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.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 30, 2010 7:01 AM   in reply to GazonkFoo

    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

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

    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.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 30, 2010 1:22 PM   in reply to GazonkFoo

    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

     
    |
    Mark as:
  • Currently Being Moderated
    Calculating status...
    Dec 17, 2010 2:05 AM   in reply to SaurabhCheenu

    +1 vote for 64bit Support.

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 19, 2010 5:57 PM   in reply to SaurabhCheenu

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

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 29, 2010 9:41 AM   in reply to Andrew Shorten

    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

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 16, 2011 10:21 AM   in reply to SaurabhCheenu

    +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

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 17, 2011 4:37 PM   in reply to SaurabhCheenu

    +1 here

     

    thanks

     

    Shigeru Nakagaki

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 21, 2011 8:03 AM   in reply to Pepe.FxUG

    i++;

     

    // Thanks!

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 24, 2011 7:11 AM   in reply to FengSun

    And one more for 64bit...

    +1

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 24, 2011 11:55 AM   in reply to SaurabhCheenu

    +1 vote

     

    PLEAAAAAASE!!!!!!!

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 25, 2011 10:48 AM   in reply to SaurabhCheenu

    +1 for 64bit support

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 7, 2011 9:05 AM   in reply to SaurabhCheenu

    Here is Flex JIRA entry.

     

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

     

    Let's vote this!!

     

     

    Shigeru Nakagaki

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 9, 2011 5:20 AM   in reply to SaurabhCheenu

    +1 for 64bit support.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 23, 2011 3:58 PM   in reply to ipo30

    throw my +1 in the hat too. Argh.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 23, 2011 4:01 PM   in reply to Andrew Shorten

    @Andrew,

    > 6 months have gone by since your post about monitoring for the need for a 64bit version, how's that going?

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 30, 2011 1:51 AM   in reply to SaurabhCheenu

    +1 for 64bit support

     

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

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 4, 2011 7:14 AM   in reply to shandsteven

    +1 for 64bit support.

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 4, 2011 7:47 PM   in reply to Krishna Kotha

    Still not enough demand?

     

    +1 for 64bit support.

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 21, 2011 6:35 AM   in reply to yif

    + 1 more for 64-bit support

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 28, 2011 7:20 AM   in reply to Grees111

    +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

     
    |
    Mark as:
  • Currently Being Moderated
    May 12, 2011 6:45 AM   in reply to SaurabhCheenu

    +1

     
    |
    Mark as:
  • Currently Being Moderated
    May 19, 2011 4:14 AM   in reply to SaurabhCheenu

    +1 for 64-bit support as well.

     
    |
    Mark as:
  • Currently Being Moderated
    May 24, 2011 9:38 AM   in reply to SaurabhCheenu

    [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]

     
    |
    Mark as:
  • Currently Being Moderated
    May 24, 2011 9:45 AM   in reply to Thomas Fowler

    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

     
    |
    Mark as:
  • Currently Being Moderated
    May 24, 2011 11:01 AM   in reply to Andrew Shorten

    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.

     
    |
    Mark as:
  • Currently Being Moderated
    May 24, 2011 11:02 AM   in reply to Andrew Shorten

    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

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 2, 2011 7:38 AM   in reply to SaurabhCheenu

    +1 for 64-bit support.

     

    Being able to use a 64-bit JRE in flash builder would be awesome. The 1gb memory limit of 32-bit eclipse/java is annoying. I get out-of-memory errors multiple times a day in FB.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 6, 2011 10:42 AM   in reply to SaurabhCheenu

    +100 votes (1 for each developer in our organization)

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 13, 2011 7:27 AM   in reply to SaurabhCheenu

    +1 for 64 flash builder!

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 5, 2011 12:42 PM   in reply to SaurabhCheenu

    +1 for x64 support!

     

    Our team is consistently working with large Flex/Air applications that integrate with many other backend technologies. Unfortunately, the memory limitations of 32 bit eclipse installations are a severely limiting factor when we are trying to work on the entirety of the project within a single workspace. Furthermore, the memory profiler in Flash Builder quickly becomes unusable during large application development because it can't get the resources it needs to run effectively.

     

    Please, Adobe, hear our cries! Give us FlashBuilder x64!

     

    -Matt

     

    P.S. Please also explain the current limitations to delivering one.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 17, 2011 9:27 AM   in reply to SaurabhCheenu

    +1 here

     

    I am running into that java heap error. And why haven't you release an IDE in AIR? Do I need to program this too? It would make the application OS independent!

     

    Thomas Pickett

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 17, 2011 1:54 PM   in reply to thestud

    Note that the FlashBuilder is an eclipse plugin and eclipse itself is OS independant (as long as SWT is supported on the platform).

    On the other hand linux support has been dropped as of AIR 2.6 - so the only supported (desktop) platforms are Windows and Mac OS.

     

    And of course there is an x64 version of eclipse as well as an x64 edition of the JRE available, which is not the case for AIR or flash in general.

     

    I think i will adobt IWantToLikeAdobe's google chrome quote as my signature on this forums:

    THE FOLLOWING TECHNOLOGY HAS BECOME UNRESPONSIVE: ADOBE FLEX

     

     

    Shame on you, Adobe!

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 22, 2011 7:48 AM   in reply to GazonkFoo

    Hi,

     

    First: Eclipse is not OS independant.

    Second: Why 64bit? Because it is starting to get hell to compile a enterprise level flex application using a 32bit process which can only use a minimal amount memory. Arrrggg.

     

    I'm working for about 6 months now for my first flex client using flex builder and already fed up with it. Back to HTML/jQuery for me.

     
    |
    Mark as:
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