Flex Builder 3 plugin don’t work with Eclipse 3.4

Eclipse 3.4 code named Ganymede just came out with some new cool features. But I have tested to install both Eclipse 3.4 and the last Flex Builder 3 plug-in from the Adobe website, and they don't work together. Eclipse can't launch Flex editor when needed. So in case you search the Internet for this info like me before, you'll find it here.

I don't know if Adobe will update Flex Builder 3 plug-in to work with Eclipse 3.3 and Eclipse 3.4 or if they will bundle Eclipse 3.4 with the incoming Flex Builder 4. I personally hope that they will update Flex Builder 3 plug-in as soon as possible and launch Flex Builder 4 bundled with Ganymede.

It probably do not requires an update as soon as possible, but now with Ganymede, you can close file tabs with middle mouse button and add new projects to their corresponding working sets in the new projects dialogs (I talk about «Working sets» recently).

Update : I have reported an issue related to this problem. It's strange because previous issues have been reported with Eclipse 3.4 M7 and are closed for now. It's probably a new problem related to the final build or Flex Builder plug-in build on the Adobe website is not to date (mine is 3.0.194161)

Adobe has now published Flex 3.0.1. It fixes the problem.

You don't need the patch anymore, I give all necessary info in another post.

Mfranczak posted a patch that fixes the problem!
  • Install Eclipse 3.4.
  • Install Flex Builder 3 as plug-in. When warned to cancel the installation because the installer did not find any Eclipse 3.2 or 3.3 installation folder, use the proceed with caution button.
  • Download the patch that Mfranczak posts (mirrored).
  • Temporary extract the archive somewhere.
  • Open your Flex Builder installation directory.
  • Backup any file with the same name and copy the two jar files of the archive into the "eclipse/plugins/" folder of your Flex Builder installation directory.
  • If you see that version or name of file you copy differ a little from any existing file, simply backup the other file and name the new with the same name (commenter JteB give us some steps to follow in the comments if your version is really not the same).
  • Start Eclipse from the command line with : eclipse -clean. It's mandatory, it will not work otherwise.

It works for me two times on different Flex Builder installation and some of you reported that it works on Linux and Windows. Enjoy the Mfranczak patch and many thanks again to him. Note that this was only tested with Flex Builder plugin, I even don't know if standalone version could automatically update to Ganymede.

We are of course all waiting that Adobe publishes an updated version of Flex Builder 3 that supports Ganymede (public access to weekly builds would be great).

92 Replies to “Flex Builder 3 plugin don’t work with Eclipse 3.4”

  1. Thanks for posting this so promptly. I just hit the same problem. The traceback I get in the editor window is:

    org.eclipse.jface.util.Assert$AssertionFailedException: Assertion failed:
    at org.eclipse.jface.util.Assert.isTrue(Assert.java:185)
    at org.eclipse.jface.util.Assert.isTrue(Assert.java:170)
    at com.adobe.flexbuilder.editors.derived.editor.FlexMultiPageEditorPart.setActivePage(FlexMultiPageEditorPart.java:569)
    at com.adobe.flexbuilder.editors.common.editor.CodeAndDesignEditor.setActivePage(CodeAndDesignEditor.java:647)
    at com.adobe.flexbuilder.editors.mxml.MXMLEditor.setActivePage(MXMLEditor.java:487)
    at com.adobe.flexbuilder.editors.derived.editor.FlexMultiPageEditorPart.createPartControl(FlexMultiPageEditorPart.java:235)
    at com.adobe.flexbuilder.editors.common.editor.CodeAndDesignEditor.createPartControl(CodeAndDesignEditor.java:162)
    at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:661)
    at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:428)
    at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:594)
    at org.eclipse.ui.internal.EditorAreaHelper.setVisibleEditor(EditorAreaHelper.java:263)
    at org.eclipse.ui.internal.EditorManager.setVisibleEditor(EditorManager.java:1410)
    at org.eclipse.ui.internal.EditorManager$5.runWithException(EditorManager.java:944)
    at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31)
    at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
    at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:133)
    at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3378)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3036)
    at org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.java:803)
    at org.eclipse.ui.internal.Workbench$27.runWithException(Workbench.java:1361)
    at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31)
    at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
    at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:133)
    at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3378)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3036)
    at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2293)
    at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198)
    at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493)
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288)
    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488)
    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
    at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
    at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1236)

  2. did anyone tried to update Flex Builder 3 to Eclipse 3.4 (i mean update from standalone Flex version using the update manager) ?

  3. Mfranczak thank you ever so much. I was tempted to do the same thing – but you saved me the trouble.


  4. @Xeepy > Sure it works, but many people working with Eclipse 3.3 will want to upgrade to Eclipse 3.4 as soon as possible. This was the meaning of this post.

  5. mfranczak, your patch didn’t work for me on a clean install of Ganymede (Java EE version) + FB3 download.

  6. I’m echoing Sagemintblue’s experience with your patch. I’m running Mac OS X 10.5.4 with JDK 1.5 + Eclipse 3.4. The patch did not work…

  7. Good morning everybody!

    I’ve the same problem, I used mfranczak’s batch, it seems it doesn’t work, the same stacktrace is shown.

    I guess the problem is just with mxml files, with ActionScript files it works like previously.

    I hope that adobe will fixe this bug as soon as possible 🙁

    Nice day.

  8. The patch works for me after renaming the files to the correct version number and unzipping the debug.e33.jar file

    Running on Gentoo with JDK 1.6.0_06

  9. Hi jteB,

    Thank you very much, for this solution, but if you explain a little bit in details it’s will be very great, and I’ll be thankfull.

    Have a nice time.

  10. @JteB > I’m really interested in this solution too if it can make Flex builder fully work with Eclipse 3.4.

  11. it isn’t working for me either. the files already had the correct version number, 3.0.194161. do you really need DTP + EMF + GEF + SDO installed as it says in the readme.txt? i noticed my original install only has debug.e32 and not e33…

    com.adobe.flexbuilder.debug.e33.jar file resides within the com.adobe.flexbuilder.debug.e33_3.0.194161.jar, so I imagine unzipping it meant taking it out of there and putting it somewhere? why? where?

    i’m on winxp, and my thinking is this only works on linux…

  12. mfranczak’s patch works.
    I just copied com.adobe.flexbuilder.editors.derived_3.0.194161.jar into Adobe Flex Builder 3 Plug-in/eclipse/plugins
    then restarted eclipse with eclipse -clean

    not sure if com.adobe.flexbuilder.debug.e33_3.0.194161.jar is needed, mxml files open fine without it.

    this is on OS X 10.5.4, Java 1.5

  13. ohh thanks Microcape! i tried it with -clean and it worked!

    so, for others: open up command prompt and navigate to your eclipse directory, then launch with
    eclipse -clean (on windows, or)
    ./eclipse -clean (on mac/linux)

    this is only necessary once. sweet. a belated thanks to mfranczak!

  14. I’d be glad to explain

    What I did,

    I extracted the files to some tmp directory (let’s call it $tmp)

    Inside there’s a folder, with some folders (if I remember correctly), the important stuff is in the subfolder eclipse/plugins

    (my case ~/coding/flex/builder_a3/eclipse/plugins $)

    Now do this:

    copy the files from the $tmp/….//plugins folder to your …/…./(SOMEFLEXBUILDERFOLDER)/eclipse/plugins folder

    list that folder, so you can check the correct version number of your installation (mine was 196042)
    As you will probably notice, the version numbers of the just extracted files don’t match those of the installed ones and you have duplicate plugins with different version numbers. This means eclipse will still use the installed ones, as those are described in the manifest …

    Let’s call your flexbuilder/eclipse/plugins folder FBP

    do the following (on *NIX (sorry, I’m not going into Windowns, I don’t have it running anywhere, so I’d have to guess the commands))

    (Backup your files by moving them)
    mv com.adobe.flexbuilder.debug.e33_3.0.196042 ~/bck
    mv com.adobe.flexbuilder.editors.derived_3.0.196042.jar ~/bck

    (Put in the new files (if you didn’t already do this)

    Now list that folder (ls -l path/to/your/flexbuilder/eclipse/plugins/folder)
    As you’ll probably notice, you now 2 jars with weird difering version numbers

    rename the com.adobe.flexbuilder.editors.derived_3.0.194something.jar to the correct name (in my case com.adobe.flexbuilder.editors.derived_3.0.196042.jar, but check your installation)

    unzip the com.adobe.flexbuilder.debug.e33_3.0.something.jar (unzip com.adobe.flexbuilder.debug.e33_3.0.something -d .)

    move (rename) the just extracted folder to the correct folder. Again in my case:

    mv -f com.adobe.flexbuilder.debug.e33_3.0.something com.adobe.flexbuilder.debug.e33_3.0.196042

    I changed the MANIFEST file inside that folder. Although I do not really think it is necessary, it is hereby mentioned. Try first without, if it doesn’t work, try changing it:

    jteb@jaded ~/coding/flex/builder_a3/eclipse/plugins $ cat com.adobe.flexbuilder.debug.e33_3.0.196042/META-INF/MANIFEST.MF

    Manifest-Version: 1.0
    Ant-Version: Apache Ant 1.6.5
    Created-By: 1.5.0_07-87 (“Apple Computer, Inc.”)
    Bundle-ManifestVersion: 2
    Bundle-Name: Flex Debug Fragment for Eclipse 3.3
    Bundle-SymbolicName: com.adobe.flexbuilder.debug.e33;singleton:=true
    Bundle-Version: 3.0.196042
    Bundle-Vendor: Adobe Systems Incorporated
    Fragment-Host: com.adobe.flexbuilder.debug.ui
    Require-Bundle: org.eclipse.debug.ui;bundle-version=”[3.3.0,99.0.0)”
    Bundle-ClassPath: com.adobe.flexbuilder.debug.e33.jar

    Now start ganymede and have a look at your plugin options. Create a new MXML file and (hopefully) be surprised 🙂


  15. I didn’t read back before, but I think the only reason Microcape’s solution works is because the version numbers match (indeed, I can see in my manifest that it’s Mac OSX version number mentioned)

    So, I think ion any other platform than OSX you should try my solution (I’ll have to wait till monday to try on my macpro 🙂

  16. @jteb > I have the same version as the patch ( v 3.0.194161) so finally I just have to drag-drop the files recommended by mfranczak into my flexbuilder plugins folder and use the microcape eclipse -clean trick and it works ! 🙂

    I’m sure that anyone on Linux/Max will need your explanation because versions are probably not the same between Windows/Mac/Linux. I’m personally on Windows. So, many thanks.

  17. Glad it works for you, and no problem at all.

    I have to say though that microcape’s isn’t really a trick, it’s (or at least it should be 🙂 ) common knowledge.


  18. Thanks mfranczak and microcape. It worked great for me with “-clean” on my Mac.

  19. The only bad thing I can note with this update to Ganymede is that automatic detection of inline “tasks” with keywords like “TODO”, “FIXME”, etc… don’t work anymore with Flex. It works well with Java documents, so it seems that we have to wait the official update to know if it is a bug that is already fixed in the Flex Builder trunk or not.

  20. With the update to Ganymede on the patch, Flex Builder does not remove unused imports when the option is selected.

  21. Sorry to spam you, after restarting Eclipse, my Flex Builder now well remove unused imports. I don’t know if it is an absurd Ganymede bug or Flex Builder one, but it was only temporary.

  22. can some one upload the patch again,

    i’ve tried to download from both sources but failed 🙁


  23. Pingback: Eclipse (FlexBuilderプラグイン) - Rest Term

  24. Can anyone please tell me how to install Flex builder 3 on Eclipse 3.3?
    Because, flex builder 3 comes with inbuilt eclipse….

  25. Pingback: 在Eclipse 3.4上使用FlexBuilder的方法 | 闲云孤鹤 - 清冷香中抱膝吟

  26. Pingback: 在Eclipse 3.4上使用FlexBuilder的方法 | 搜我收藏

  27. Pingback: Enno Rehling » Blog Archive » How to get Flex Builder 3 and Eclipse 3.4 Ganymede to play nice

  28. The patch worked for me with the following scenario:

    WIndows XP SP3
    IE 7
    Firefox 3.x

    -uninstall/delete all previous Flex Builder 3 plugins, and Eclipse Ganymede versions

    -install Eclipse Ganymede 3.4 standard SDK (comes with DTP,EMG,GEF, SDO as mentioned in readme)
    -install Flex Builder 3 plugin
    -backed up necessary files as per instructions
    -unzipped patch and extracted patch files into c:\Program Files\Adobe\Flex Builder 3 Plug-in\eclipse\plugins
    -launched Eclipse from command prompt with -clean parameter

    -also works by adding -clean parameter to the Adobe/Eclipse Flex Builder Plugin shortcut in the start menu (just right click on the icon, choose properties, add the -clean parameter)


    Edward Apostol, Senior Instructor, Consultant
    Certified Adobe Flex Instructor
    New Toronto Group

  29. Thank you very much, It worked fine for me.

    I just need to rename com.adobe.flexbuilder.debug.e33_3.0.194161 to com.adobe.flexbuilder.debug.e32_3.0.194161.

    C ya

  30. pedro> just need to rename com.adobe.flexbuilder.debug.e33_3.0.194161 to com.adobe.flexbuilder.debug.e32_3.0.194161.

    Yes, it was exactly what I mean with “If you see that version or name of file you copy differ a little from any existing file”. 🙂

    Depending on the file you’ve downloaded from the Adobe website, or if you use an archived installer the version can differ a little. I hope they will soon push a version that supports Ganymede.

  31. Hello.
    There is new Flex Builder 3.0.205647 (eclipse/help/Search for Flex Builder updates) which works with Eclipse 3.4.

    Best regards

  32. Many thanks for all again Mfranczak.

    For my part when I’ve tested to update Flex Builder from Eclipse 3.3, it does nothing. No process is running in background, nothing.

  33. >For my part when I’ve tested to update Flex Builder from Eclipse 3.3, it does nothing. No process is running in background, nothing.

    Check your %LOCALAPPDATA%\Adobe\Updater5\install\ folder, search for downloaded FB3_Updater.exe (Win).
    This update also contains Flex SDK 3.1.

  34. @Mfranczak>Between my post and your answer, I simply have tested to download the last Flex Builder plug-in from the Adobe website. And all works well. You don’t need to patch anymore.

    I will investigate more but it seems that Eclipse tasks (TODOs, FIXMEs) don’t work anymore in this release as in the patched release.

  35. Just tried the new alpha 4 for Linux with Eclipse 3.4 (Ganymede), and I get that Assertion failed error when I try to open an mxml file. Opening *.as files works well. I tried applying the patch above (which worked well with a3), but then the whole Flex perspective failed to load, maybe the patch doesn’t work with alpha 4? Can anybody provide a new patch for a4? Using Ganymede is crucial to me…

  36. Pingback: Java Beans dot Asia

  37. Hi,

    using the JEE edition of 3.4.1 and FB Plugin 3.0.1. On OS-X Leopard with all latest updates.

    1) unzip a brand new eclispe install
    2) run the plugin installer

    1/2 way through the install I get this error:
    “This installation can still be configured manually as a Product Extension” and it gives instructions on how to manually add the plugin and to check the error log

    I hit ok, then it brings up “a newer file named “com.adobe.flexbuilder.debug.e33_3.0.205647.jar” already exists at “/Applications/Adobe Flex Builder 3 Plug-in/eclipse/plugins” Do you want to overwrite this file?

    The error log has the following in it:

    !SESSION 2008-10-22 08:54:01.197 ———————————————–
    java.vendor=Apple Inc.
    BootLoader constants: OS=macosx, ARCH=x86_64, WS=carbon, NL=en_US
    Framework arguments: -application org.eclipse.update.core.standaloneUpdate -command install -featureId com.adobe.flexbuilder.feature.core.osx -version 3.0.205647 -from file:/Applications/Adobe Flex Builder 3 Plug-in/com.adobe.flexbuilder.update.site/ -to /Applications/Adobe Flex Builder 3 Plug-in
    Command-line arguments: -application org.eclipse.update.core.standaloneUpdate -command install -featureId com.adobe.flexbuilder.feature.core.osx -version 3.0.205647 -from file:/Applications/Adobe Flex Builder 3 Plug-in/com.adobe.flexbuilder.update.site/ -to /Applications/Adobe Flex Builder 3 Plug-in

    !ENTRY org.eclipse.update.core 4 0 2008-10-22 08:54:07.016
    !MESSAGE Featurecom.adobe.flexbuilder.feature.core.osx 3.0.205647cannot be found onfile:/Applications/Adobe Flex Builder 3 Plug-in/com.adobe.flexbuilder.update.site/
    or a newer version is already installed.

    So…. I then startup eclipse and go to open perspective. Nothing there for Flex. So I go to software updates and point to the Flex Builder plugin install folder/eclipse as instructed in the installer error. I setup this new “local site” and proceed to “install” the flex builder plugin through the software update mech.

    “calculating requirements and dependencies….” The software items you selected may not be valid with your current selection…

    Cannot complete the request. See the details.
    Unsatisfied dependency: [com.adobe.flexbuilder.debug.e32 3.0.205647] requiredCapability: osgi.bundle/org.eclipse.debug.ui/[3.2.0,3.3.0)
    Unsatisfied dependency: [com.adobe.flexbuilder.feature.core.osx.feature.group 3.0.205647] requiredCapability: org.eclipse.equinox.p2.iu/com.adobe.flexbuilder.debug.e32/[3.0.205647,3.0.205647]
    Unsatisfied dependency: [com.adobe.flexbuilder.feature.core.osx.nl1.feature.group 3.0.205647] requiredCapability: org.eclipse.equinox.p2.iu/com.adobe.flexbuilder.feature.core.osx.feature.group/[3.0.205647,3.0.205647]
    Unsatisfied dependency: [com.adobe.flexbuilder.debug.e32 3.0.205647] requiredCapability: osgi.bundle/org.eclipse.debug.ui/[3.2.0,3.3.0)

  38. Pingback: Installer le plugin Flex pour eclipse sous Linux | Formation Flex

  39. Onanga, which Eclipse version did you use on Linux? Didn’t work for me with Ganymede JEE.

  40. This is working for me now on Mac OS X 1.5.5 (Leopard).

    Installed Eclipse 3.4 (Ganymede)
    Installed Flex Builder 3 Plugin (from the CD)
    Ran the Adobe Updater to get Flex Builder
    Created a new workspace (-clean would probably do the job also)
    Created a new Flex Project
    Edited the application MXML and it works.

    I’m using java version “1.5.0_13”

  41. I am new to flex dev, I just start.

    First I install flex (build: 3.0.194161) to use with Eclipse 3.2.1, it’s working fine.

    I wan to use my existing flex plugin with Eclipse 3.4, I got problem as describe in this post.

    I wanna to try to use both eclipse with the same flex plugin, with Eclipse 3.4 I try to install Flex plugin by Software Updates but I could not.

    I tried the patch in this post but I still can’t get success by add the external plugin to Eclipse 3.4, first I though this patch is not working…

    Finally, I uninstall the Flex plugin and then following comment of (Edward Apostol [ 12 août 2008 13:20 ]) by using this patch, it’s working now.

    Thanks for the patch but if any one find solution possibly to install flex plugin with Software Updates of Eclipse 3.4 work without error would be very great, I just want to know it.

  42. MTR, you just have to install the plug-in by downloading the last version from the Adobe website to make it work. You don’t need the patch anymore.

  43. Can’t install Flex Builder 3.0.2 in Eclipse 3.4 (Ganymede) on MacOS X. I de-installed the previous installation, ran the installer, then I get a “did not complete..see log file” message, log file says “!MESSAGE Featurecom.adobe.flexbuilder.feature.standalone.osx 3.0.214193cannot be found onfile:/Applications/eclipse/Adobe Flex Builder 3/com.adobe.flexbuilder.update.site/
    or a newer version is already installed.”

    Installer allows me to continue, but when complete, installer says “Important: thee was a problem installing Flex Builder features into Eclipse”. And that’s true, it’s not available in Eclipse.

    If I try to launch the FB3 standalone, I get a log with: !ENTRY org.eclipse.osgi 2 0 2008-12-19 14:45:59.158
    !MESSAGE The following is a complete list of bundles which are not resolved, see the prior log entry for the root cause if it exists:
    !SUBENTRY 1 org.eclipse.osgi 2 0 2008-12-19 14:45:59.158
    !MESSAGE Bundle update@plugins/org.eclipse.datatools.connectivity.oda.template.ui_3.0.4.200706071.jar [51] was not resolved.
    !SUBENTRY 2 org.eclipse.datatools.connectivity.oda.template.ui 2 0 2008-12-19 14:45:59.158
    !MESSAGE Missing required bundle org.eclipse.pde.ui_[3.2.0,4.0.0).

  44. If you are using linux and want to get the a4 build running with eclipse 3.4 then you just have to rename the two jar files in the patch to match the new plugin names :

    i.e. the new names should be :


    I put those two jars in the main eclipse plugins directory, then moved the originals out of the flexbuilder plugins directory (i didnt delete them, just moved them..you never know if you might need them again..)

    I restarted eclipse and its all running well so far, mxml editing, as editing and the debugger is working (at least from my preliminary tests). Im on Ubuntu 8.10 32-bit.

  45. Thanks for posting these instructions! I am able to get the patch installed so that it now is no longer showing the assertion error when looking at mxml files. However, I can only look at it in source view, there is no design view available anymore (the view chooser in the lower left corner of the code window is no longer there).

    Is this the intention of the patch (to effectively remove design view)? I was under the impression that this patch actually fixed the design view issues.


  46. Can someone confirm for me that they got this working on Linux using the linux flexbuilder alpha 4 from adobe?
    After applying the patch above I can see the code view, but there is no option to switch to design view from what I can tell.

  47. Found this snippet on the adobe labs site just after posting:
    * Design view
    * States view
    * Refactoring
    * Data Wizards
    * Cold Fusion – Data Services Wizard
    * Web Services introspection
    * Profiler

    How unfortunate. 🙁

  48. heres a recap for:

    linux / Eclipse 3.4.1 / Flexbuilder a4:

    1. Download the Mfranczak patch
    2. Rename the patch’s jar files to the correct versions.
    3. Copy the two patch files into your eclipse/plugins folder (overwriting the older jars, or you can back the older ones up if you want)
    4. Delete the debug.e33 folder and extract the debug jar
    5. restart eclipse with -clean startup parameter (eg. “eclipse -clean” )

    In my case i upgraded my current eclipse to 3.4 on ubuntu (/usr/lib/eclipse) and installed flex into /usr/lib/flex then chown’d both of those directories recursively so i could read/write as i please…. then i went into eclipse and created a new local update site, pointing it to /usr/lib/flex/com.adobe.flexbuilder.update.site and installed everything from there. afterwards i followed those steps to get it to work

  49. Pingback: Desenvolvimento no Linux (Eclipse 3.4 + plug-in Adobe Flex Builder 3) « Luciano Santos

  50. As Realgt said:
    1. I got eclipse 3.4
    2. installed flex builder alpha 4 for linux
    3. chowned eclipse and flex locations
    4. tried to enter in eclipse to create local update site and to install flex builder from there but the eclipse did not stared exiting with log about lots of flex builder unresolved jar files.

    Tried to make it manually
    1. Downloaded the Mfranczak patch
    2. Backuped the original files which are:
    and directory com.adobe.flexbuilder.debug.e33_3.0.204732
    3. Renamed and Copy the two patch files into eclipse/plugins folder
    4. extract com.adobe.flexbuilder.debug.e33_3.0.204732.jar

    5. And when i execute “eclipse -clean” the same unresolved flex builder related jar files appear.

    Opensuse 11.1 and i use Ganimed which comes with the distro.
    Hmm am i missing sth here !?!? Did somebody have experience with unresolved files after installing flex builder ?

  51. @Atanas,

    so you never created the update site in eclipse that points to flex/com.adobe.flexbuilder.update.site ? If not you probably are missing the features folder (/usr/lib/eclipse/features/com.adobe.flexbuilder.feature.core.linux_3.0.204732).

    also, i would delete everything in features or plugins relating to flex and try again by creating a local site and pointing it to that update folder that comes with flexbuilder a4 (com.adobe.flexbuilder.update.site)

    good luck

  52. Pingback: DiarioLinux » Flex Builder 3 para Linux: el gran olvidado de Adobe

  53. Dear All

    I’m getting the same error (Could not open the editor: Assertion failed: ) with Ganymede (Version: 3.4.2 Build id: M20090211-1700) and Flex Builder Linux Version: 3.0.204732 on Fedora 9.

    You state the error is fixed in 3.0.1. Is it likely to have reappeared in 3.0.2?

    Will applying the patch help?



  54. Suren

    Many thanks for the link. I’ll try it and let you know if there are any problems.


    Many thanks


  55. Suren

    Removed the eclipse and flexbuilder installations and then tried the instructions you provided. I still get the same error. Can you confirm that 3.0.2 works with eclipse 3.4.2?
    Is it likely to be affected by the OS (Fedora 9)?

    I’ve also tried installing the additions suggested in the readme that comes with the patch (GEF etc).

    I’ll try applying the patch again.


  56. Hi Suren

    I tried installing the patch as per the instructions above. The system now works fine.

    Thanks for all your help.



  57. Pingback: Patch for Flex builder 3 with Eclipse 3.4 Ganymede « Ajo Paul

  58. Thank Mfranczak! It’s done with my eclipse 3.4 on Windows 🙂

  59. Pingback: Eclipse 3.5 (Galileo) and Flex Builder for Linux…working! « blog.danyul.id.au

  60. Pingback: Installer le plugin Flex pour eclipse sous Linux | LyRiX Blog

  61. Dear All

    I now have Flex Builder (Ganymede (Version: 3.4.2 Build id: M20090211-1700) and Flex Builder Linux Version: 3.0.204732) running on Fedora 11, but have no buttons to toggle between source and design views (and no access to design view).

    Is this a bug? I see that a number of people have commented saying they are/were waiting for design view in FB for Linux (here for example: http://bugs.adobe.com/jira/browse/FB-19053;jsessionid=3EBE25E74B4DC6B0DAB08DA77CF17ED8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel). Does this mean it’s (Design View) still not available?

    If it’s a bug can anyone help/suggest anything to fix it?



  62. Pingback: Flex-Builder-Linux kein MXML-Editor - Flashforum

  63. Pingback: How to start programming Flash under Linux, using Open Source tools where possible? | do IT!

  64. Pingback: Linux Flex Builder DEAD? No

  65. Pingback: How to start programming Flash under Linux, using Open Source tools where possible? « Mind of Matt

Leave a Reply

Your email address will not be published. Required fields are marked *


* Please Add the Values