Flex Builder 3 on Eclipse 3.5

I recently tried to upgrade to Eclipse 3.5 on my Ubuntu Linux desktop. Unfortunately this caused some problems with the Flex Builder 3 for Linux alpha 4. According to the stack traces in Eclipse the main problems seemed to stem from the com.adobe.flexbuilder.project.compiler.internal.ProblemManager class. So I decided to re-write that class from scratch to see if I could make the problems go away. My new implementation of ProblemManager seems to have fixed the issues that I was seeing. I’ve only tested this on Linux so I’m not sure if it will fix any problems on Mac or Windows. Here are the instructions for fixing the problems with Flex Builder 3 on Eclipse 3.5 on Linux:

  1. Make sure you have installed Eclipse 3.5 and the Flex Builder 4 for Linux alpha 4
  2. Download the ProblemManager patch
  3. Unzip the ProblemManager patch file
  4. Locate where Flex Builder is installed – in my case: ~/flex_stuff/Adobe_Flex_Builder_Linux
  5. Update the com/adobe/flexbuilder/project/compiler/internal/ProblemManager.class file in <Flex Builder Install Location>/eclipse/plugins/com.adobe.flexbuilder.project_3.0.204732/zornproject.jar with the file extracted from the patch
  6. Start Eclipse 3.5
  7. Smile!

UPDATE: Instructions for Windows were posted on InsideRIA by Mike Slinn. Thanks Mike!

So far this works for me. But I’m sure there are some problems I haven’t discovered with it yet. So please let me know if you have any problems. Also if someone wants to check this on Windows or Mac let me know if it works there. If not then feel free to update the ProblemManager.java class so that it does work.

DISCLAIMER: This patch is totally unsupported by Adobe. Use at your own risk.

This entry was posted in Flex. Bookmark the permalink. Post a comment or leave a trackback: Trackback URL.

43 Comments

  1. Posted September 30, 2009 at 8:03 am | Permalink

    Thanks! It worked a treat… Now I can use Galileo & vimplugin to do flex dev … yay :)

  2. equan
    Posted October 2, 2009 at 9:20 am | Permalink

    thank’s for share it james! :)

  3. Julien Nicoulaud
    Posted October 8, 2009 at 2:36 am | Permalink

    Works like a charm, thanks a lot !

  4. Julien Nicoulaud
    Posted October 8, 2009 at 4:42 am | Permalink

    After all there is something: could you recompile it with a JDK 5 ? I get this error on my workspace error’s log:
    Errors running builder ‘Flex’ on project ‘test’.
    java.lang.UnsupportedClassVersionError: Bad version number in .class file
    … bla bla ….
    at com.adobe.flexbuilder.project.compiler.internal.FlexIncrementalBuilder.getProblemManager(Unknown Source)

    So I guess it was compiled with a JDK 6…

    Regards

  5. Posted October 8, 2009 at 6:49 am | Permalink
  6. Julien Nicoulaud
    Posted October 8, 2009 at 7:00 am | Permalink

    Perfect, it now runs over a JDK 5.
    Regards ;)

  7. Posted October 14, 2009 at 4:33 am | Permalink

    Thanks James! I was starting to go insane with all the errors Flex kept generating after i upgraded to Eclipse 3.5. Or maybe it was the fact that it often just refused to compile swf when you told it to run. Spend to many hours trying to fix this.

    -Daniel

    PS: Come back to Copenhagen soon!

  8. Christophe .D
    Posted October 14, 2009 at 2:41 pm | Permalink

    Hi,
    I have the same problem but I’m using Flex Builder 3 with Eclipse 3.5 Galileo on windows.
    I looked on many forum about this problem, but no solution was found except your patch.
    So I tried it but I still have the issue.
    So could you help me ? Could you said me how you have recompiled the class … according all dependencies !
    Because I started to do it, by getting java from ProblemManager.class, but there is a lot of dependencies .
    An other thinks is strange : Your problemManager.java => 233 lines. instead of the original problemManager.java =>481 lines

    Regards,
    Christophe D.

  9. Christophe .D
    Posted October 15, 2009 at 2:45 am | Permalink

    Hi,
    I tried again your patch, And now it works. In fact the first time I updated the FlexBuilder folder (FlexPlugin\eclipse\plugins\com.adobe.flexbuilder.project_3.0.214193).
    But Eclipse Galileo have made a local copy of all required lib inside plugin folder at the installation.
    So I try to copy directly zornproject.jar updated with your patch to Eclipse3.5/plugins/com.adobe.flexbuilder.project_3.0.214193 and now it’s seems working.

    Just a question have you cleanned lot of code ? because Your problemManager.java => 233 lines instead of the original problemManager.java =>481 lines

    Thanks a lot, great job !!.
    Christophe.D

  10. Posted October 16, 2009 at 9:10 am | Permalink

    Hey Christophe,

    Glad you got it working! I’m not sure what the original ProgramManager.java class did or what it looks like. So I’m not sure why mine is so much smaller.

    -James

  11. Max
    Posted October 22, 2009 at 12:00 am | Permalink

    Thankyou very much.

    Its a real shame that development of Flexbuilder on Linux seems to have died.

    Sure that you can’t comment James but i just wanted to register my complaint.

  12. Rajeev Goel
    Posted November 2, 2009 at 10:18 pm | Permalink

    Hi,

    Tried the patch, but it fails due to incompatible Java version in class file.
    I suspect that happens because I run eclipse with java 1.5 and class may have been compiled with 1.6.
    Our project hasn’t migrated to use 1.6 yet.

    James could you please compile and publish for 1.5 ? That should not be too difficult ;)

    thanks !
    Rajeev

  13. Posted November 3, 2009 at 5:41 am | Permalink

    Hi Rajeev,

    See the comments above for the 1.5 version. Let me know if that works.

    -James

  14. Rajeev Goel
    Posted November 4, 2009 at 4:03 am | Permalink

    it works, thanks ! Your help is most appreciated.

  15. Iker Martin
    Posted November 13, 2009 at 5:53 am | Permalink

    Great it works! Thanks a lot!

  16. Posted November 14, 2009 at 1:51 pm | Permalink

    I was about to give up entirely until i found your post! You are a saint, a scholar and a demi-god. :-p

    And i owe u that beer.

  17. KillerSpaz
    Posted November 16, 2009 at 10:22 am | Permalink

    This patch fixed the “An internal build error has occurred” error, but I am getting an error defined as “Classes must not be nested”. I know this is common with empty switch statements, but in my basic application (literally just a vbox, with text, and an applicationComplete handler to set the style [cheezy test for something]) and I get this error and can’t launch or fully compile it.

    Any ideas?

  18. Greg Meddles
    Posted November 18, 2009 at 4:45 pm | Permalink

    Thanks for sharing. I got it working with for Mac OS X using JavaEE Galileo Carbon 32bit with Flex Builder 3.

  19. Justin Lee
    Posted November 23, 2009 at 12:46 pm | Permalink

    Thanks for the fix! Works great on Windows XP, Galileo Eclipse 3.5 and Flex Builder 3.4.

    You have to update zornproject.jar in C:\Program Files\Adobe\Flex Builder 3 Plug-in… directory as well as the eclipse installation directory (i.e. C:\eclipse\plugins\com.adobe.flexbuilder.project_3.0.214193)

    Also, add “-clean” to eclipse.ini and restart.

    It’s too bad Adobe won’t fix this. See:

    http://bugs.adobe.com/jira/browse/FB-21284

    Thanks again,
    Justin

  20. Iker Martin
    Posted November 24, 2009 at 10:58 am | Permalink

    Sorry for my English, I have a question, it’s Flex Builder 3 for Linux definitely dead for Adobe?, i have installed the flex builder in a eclipse galileo in ubuntu. The message of Linux Builder Expires in 6 days, it’s true? i can’t purchase it?
    Thanks.
    Iker Martin – Barcelona (Spain)

  21. Posted November 25, 2009 at 8:22 am | Permalink

    Hi Iker,

    There is an update that will extend it for another 401 days:
    http://www.jamesward.com/2009/11/25/flex-builder-on-linux-update/

    -James

  22. Posted December 3, 2009 at 6:01 am | Permalink

    I’m using the new Flex Builder Linux 5. I have com.adobe.flexbuilder.project_3.0.257568 instead of the version you said (com.adobe.flexbuilder.project_3.0.204732).
    On applying the patch, eclipse presents error on initializing.

    It’s strange as a friend of mine with the same laptop and installation process doesn’t have this issue.
    Also, this issue is only appear in on project.
    Any ideas ?? Thanks in advance.

  23. Posted December 3, 2009 at 6:18 am | Permalink

    Hi tiago,

    I also have com.adobe.flexbuilder.project_3.0.257568 now and the patch still seems to work fine. What is the error? Can you look in the /.metadata/.log file and email me the error (or post it here if it’s small)?

    -James

  24. Posted December 3, 2009 at 7:13 am | Permalink

    James,

    Trying to send you the log I went a bit more up then what I’ve already saw. And notice a zip error.
    I used a graphical app to zip back the jar … that was my problem.
    Zipping on the command line worked like a charm.

    Thanks a lot for this patch :)

    Tiago

  25. Victor Muguerza
    Posted December 12, 2009 at 7:45 pm | Permalink

    Thanks a lot for sharing James, it works very well.
    Greetings from Peru

    -Victor

  26. Ritesh
    Posted December 14, 2009 at 4:28 pm | Permalink

    Awesome.. thanks for the posting..It works with Win XP , Eclipse Galileo 3.5SR1 like a charm…

    thanks again..

  27. Otto
    Posted December 17, 2009 at 8:08 am | Permalink

    Thanks to this I’m now running Galileo and Flex 3 on Snow Leopard. Much appreciated.

  28. Los
    Posted December 21, 2009 at 9:04 am | Permalink

    Hi all,

    I gave all the above a try without much success. I’m running Eclipse SDK 3.5.0 build I20090611-1540 and the Flex Builder Plugin 3.0.214193. I’ve prepended that “path=” in the eclipse configuration, replaced the ProblemManager class as described above (using both 7zip and the jar command line), but nothing will work. All I get is the “Unable to create the selected preference page. An error occurred while automatically activating bundle com.adobe.flexbuilder.editors.common (281).” message everytime I try to switch to a Flex perspective.

    I’m also seeing a no class found exception regarding com/adobe/flexbuilder/utils/osnative/NativeControl.

    The only thing I see different when compared to the other posts is that I’m using the 64-bit versions of Eclipse and JVM. I don’t think this would have any effect on the problem, but I could be wrong. Any help would be appreciated. Thanks!

  29. Posted December 21, 2009 at 11:35 am | Permalink

    Hi Los,

    Did things somewhat work before you hacked the jar file?

    -James

  30. Los
    Posted December 21, 2009 at 11:53 am | Permalink

    I guess “somewhat work” is relative. Nothing really worked before or after (it seems). The only thing that seemed to work was when I had to prepend the location of the plugin with the “path=” in the eclipse config. This made the Flex menus and perspectives appear in Eclipse. But when I click on any of these menu items or perspectives, I get that ui error. Hacking the jar file didn’t seem to do anything.

  31. Posted December 21, 2009 at 2:31 pm | Permalink

    Los,

    It seems like you have problems beyond what my patch does. It could be the 64-bit thing or it could be a bad install. I’ve never tried on 64-bit. The only thing that my patch fixes is problems with the ProblemManager. Everything else should work as usual before my patch is applied.

    -James

  32. Los
    Posted December 21, 2009 at 3:00 pm | Permalink

    I may try a new reinstall of the plugin later today. BTW, do you know if the plugin ever works on a 64-bit Eclipse/JVM? Seems like it should now since 64-bit has been out for quite a while. If not, will Flash Builder 4 be compatible?

  33. Posted December 21, 2009 at 3:08 pm | Permalink

    I’m not sure if FB supports 64-bit. I’m on Linux where 64-bit is unnecessary with the PAE kernel. What OS are you on?

  34. Los
    Posted December 21, 2009 at 3:51 pm | Permalink

    win 7 home prem 64. I won’t be able to downgrade to 32 bit too if needed to get FB3 working since all of our machines are spec’d that way.

  35. Los
    Posted December 22, 2009 at 8:05 am | Permalink

    I reinstalled the plugin last night and the same result– does not work. I may try downgrading Eclipse/JVM to 32-bit if I ever get the time but for now I guess its good ole fashion notepad!

  36. Posted December 28, 2009 at 5:23 am | Permalink

    Thanks a lot for this great patch James!

  37. Posted January 6, 2010 at 3:22 am | Permalink

    Thank you both James & Mike for this patch and explanations, these errors really drove me crazy!
    For information, my configuration is Win7 64bits, Galileo 3.5.1.R35x_v20090910 (32bits), Flex 3.0.214193.

    I have a side-question: it seems that the compiler only displays one error at a time instead of displaying all as with the previous Eclipse version; do you have the same behaviour? I don’t know if it comes from your ProblemManager implementation or if it is linked to new Eclipse version… Thanks for your help!

  38. Posted January 6, 2010 at 8:59 am | Permalink

    Hi JeremyR,

    That happens for me as well. Pretty annoying. I haven’t had time to look into it. But if anyone wants to take my code and fix it, that would rock!

    -James

  39. Posted January 7, 2010 at 10:01 am | Permalink

    Thanks for your answer James!
    Really annoying but maybe it doesn’t come from your code but from Galileo, don’t you think?

  40. Posted January 7, 2010 at 10:08 am | Permalink

    I’d like to think that’s true but I think it’s more likely my code. I built my implementation without any knowledge of how the problems get reported. So it’s likely something I overlooked / didn’t understand.

  41. mc
    Posted January 24, 2010 at 8:01 pm | Permalink

    Hi im new to eclipse+flex builder i got this error every time i create a flex project i got this following errors:

    The selected wizard could not be started.
    Plug-in “com.adobe.flexbuilder.apollo.ui” was unable to instantiate class “com.adobe.flexbuilder.apollo.ui.wizards.flex.FlexApolloProjectWizard”.
    com/adobe/flexbuilder/project/actionscript/IMutableActionScriptProjectSettings

    Then when im going to window->preferences-> for sdk installation i got this error:

    Unable to create the selected preference page.
    An error occurred while automatically activating bundle com.adobe.flexbuilder.ui (526).

    what is going on with my installation?thanks. any suggestion please??? keep safe

  42. Venkatesh
    Posted January 25, 2010 at 12:12 am | Permalink

    The above procedure is not working for me
    I am using ubuntu 9.10, eclipse galileo, flex builder 3 for Linux alpha 4
    I am not getting mxml editor it’s showing assertion failed error
    please give the suggestion

  43. Posted February 6, 2010 at 7:59 am | Permalink

    Hi Venkatesh,

    Try this:
    http://blog.danyul.id.au/?p=68

    -James

4 Trackbacks

  1. [...] least one other person). If you find yourself with this problem then please check out his blog post here for the solution. As always, feedback is appreciated. Good work [...]

  2. By Flex Builder on Linux Update on November 25, 2009 at 6:32 am

    [...] Adobe has posted an update for Flex Builder on Linux which was scheduled to time-out on December 1, 2009. While the Flex SDK has always worked on Linux, development is certainly easier with Eclipse support for coding, compiling, and debugging. This alpha 5 release of Flex Builder for Linux allows us Linux folks to continue building Flex applications in Eclipse for another 401 days. However, Adobe has still not announced any plans to create a full Flex Builder (or Flash Builder) product for Linux. If that is something you want then please go vote for FB-19053. This update still doesn’t support Eclipse 3.5. If you want Eclipse 3.5 support then you will need to apply patches created by Danyul and myself. [...]

  3. [...] So, if you’re keen on trying it out then go ahead, you will probably still be best to follow the step I outlined in a previous post as well as use a patch created by James. [...]

  4. [...] James Ward’s ProblemManager patch (steps 2,3,4,5). A preliminary solution is to switch off warnings in the “project properties [...]

Post a Comment

Your email is never published nor shared. Required fields are marked *

*
*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> <pre lang="" line="" escaped="">

Subscribe without commenting

  • About James Ward



    View James Ward's profile on LinkedIn

  • First Steps in Flex by James Ward and Bruce Eckel




  • Twitter Updates


  • Tour de Flex