-
LAB
-
LIENS
-
RECHERCHE
Accueil - Flex Builder 3 plugin don’t work with Eclipse 3.4
Dernière révision :
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)
- 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).
Comments
@mark > I probably have the same traceback.
For my part, I urgently need to reinstall Eclipse 3.3 to work with Flex. Could you post your traceback as a comment on the issue I just have opened here : https://bugs.adobe.com/jira/browse/FB-13155
Many thanks.
Hello 
You have try FDT too ? Or only Flex with the last version of Eclipse ?
eKA+
@ekameleon > I do not own FDT, I only try Ganymede with Flex builder 3.
did anyone tried to update Flex Builder 3 to Eclipse 3.4 (i mean update from standalone Flex version using the update manager) ?
The issue that I have reported has been closed, Kazue Watanabe from Adobe tells that it has been fixed in the last Flex 3.0.1 build : http://bugs.adobe.com/jira/browse/FB-13155
It seems that we sadly cannot download Flex builder 3 nightly builds (or I don’t know where).
Try this (unofficial):
http://alan.umcs.lublin.pl/~gumi/eclipse/FB3_Eclipse34_patch.zip
That patch is not working for me.
Mfranczak thank you ever so much. I was tempted to do the same thing - but you saved me the trouble.
Cheers.
It seems Flex Builder 3 plug-in can work with Eclipse 3.3
@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.
mfranczak, your patch didn’t work for me on a clean install of Ganymede (Java EE version) + FB3 download.
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…
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.
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
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.
@JteB > I’m really interested in this solution too if it can make Flex builder fully work with Eclipse 3.4.
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…
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
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!
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
Regards,
Jan
Hmm, part of my message disappeared …
If you need further help, you can contact me at jan AT dutchsoftware DOT com
And please check out http://elvisready.com 
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
Thanks Jteb I will try this evening as soon as I can.
I will give you some feedback here.
@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.
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.
Regards,
Jan
(http://elvisready.com)
(The -clean part I mean)
Thanks mfranczak and microcape. It worked great for me with “-clean” on my Mac.
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.
With the update to Ganymede on the patch, Flex Builder does not remove unused imports when the option is selected.
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.
can some one upload the patch again,
i’ve tried to download from both sources but failed
thanks
@Tok> It works well for me here : http://www.tekool.net/blogfiles/flex-builder-3-plugin-dont-work-with-eclipse-34/FB3_Eclipse34_patch.zip
[…] 先月、Eclipseの新しいバージョンの3.4(Ganymede)が出ました。 それで今日アップデートしたんですが、そしたらなんとFlex開発ができない！ mxmlエディタが開けませんとかいろいろエラーが出てしまいました。。 どうやら3.4だとFlexBuilderプラグインが対応してないようです。 そりゃないぜということで調べてみると、非公式のパッチが出てました。 Flex Builder 3 plugin don’t work with Eclipse 3.4 […]
Can anyone please tell me how to install Flex builder 3 on Eclipse 3.3?
Because, flex builder 3 comes with inbuilt eclipse….
thanks Mfranczak, works great on MAC 10.5.4.
[…] Eclipse 3.4发布已经有一段时间了，其带来很多新的特性，但是对于使用FlexBuilder的朋友来说，想要切换到Eclipse 3.4就没那么容易，因为FlexBuilder是基于Eclipse 3.3的，和Eclipse 3.4并不兼容，在Eclipse 3.4刚发布的时候我就做过尝试，可是mxml编辑器却不能打开，会报org.eclipse.jface.util.Assert$AssertionFailedException: Assertion failed，当时没有时间折腾，Adobe官方关于这里Bug的说明在这里，这里据说在FlexBuilder 3.01已经解决了这样的问题，可那里有3.01下载，对不起，我也不知道。今天无意发现了这里，这里提供了一个补丁，利用这个我们就可以在Eclipse 3.4上使用FlexBuilder了。安装方法如下： […]
[…] Eclipse 3.4发布已经有一段时间了，其带来很多新的特性， 但是对于使用FlexBuilder的朋友来说，想要切换到Eclipse 3.4就没那么容易，因为FlexBuilder是基于Eclipse 3.3的，和Eclipse 3.4并不兼容，在Eclipse 3.4刚发布的时候我就做过尝试，可是mxml编辑器却不能打开，会报 org.eclipse.jface.util.Assert$AssertionFailedException: Assertion failed，当时没有时间折腾，Adobe官方关于这里Bug的说明在这里，这里据说在FlexBuilder 3.01已经解决了这样的问题，可那里有3.01下载，对不起，我也不知道。今天无意发现了这里，这里提供了一个补丁，利用这个我们就可以在Eclipse 3.4上使用FlexBuilder了。安装方法如下： 首先从这里下载这个补丁包： wget http://www.tekool.net/blogfiles/flex-builder-3-plugin-dont-work-with-eclipse-34/FB3_Eclipse34_patch.zip 然后解压该补丁包，解压后在Flex Builder 3 Plug-in/eclipse/plugins应该有两个文件： […]
[…] did find a solution here (make sure to restart eclipse with -clean afterwards), but this kind of fiddling with the […]
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)
cheers!
Edward Apostol, Senior Instructor, Consultant
Certified Adobe Flex Instructor
New Toronto Group
these instructions work great for me. thanks a bunch! stef
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
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.
Hello.
There is new Flex Builder 3.0.205647 (eclipse/help/Search for Flex Builder updates) which works with Eclipse 3.4.
Best regards
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.
>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.
@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.
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)