During FOTB someone asked if the Red5Plugin worked with Ganymede. My answer was “yes”, but I was unsure of whether Flex Builder worked with Ganymede. Someone else explained that it did work, so I conceded only to try again to setup my workspace using eclipse 3.4. Again, I was unable to get the Flex Builder Plugin to install. I tried to install it from the installation file as well as from a local site. Both failed with errors. So if anyone… ANYONE has gotten this to work, please speak up. I’d like to know what you’ve done differently! If you’ve had the same troubles, I’d also like to hear so that I can confirm my results. Last, if there is any official word on this, please post that as well. Thanks all!
I had no problems installing it. Adobe did release an update to Flex Builder 3 to allow it to work with Gandymede, so if you were using an older version of Flex Builder to install it, that may be the source of your problem.
I downloaded the classic eclipse version from Eclipse’s site, extracted that to my eclipse location, and installed the newest Flex Builder 3 eclipse plug-in and had no issues.
I did have to work through a little issue getting Subclipse to work in Gandymede, which I documented on my blog: http://blog.smartlogicsolutions.com/2008/08/21/getting-subclipse-to-work-in-gandymede-eclipse-34/
Good luck!
HI there.
Upgraded to Eclipse 3.4 Gandymede yesterday and installed both Flex Builder (and Subclipse for that matter) without any problems at all. I didn’t do anything out of the ordinary, I just ran the installer.
I’m having problems getting Eclipse 3.4 and Flexbuilder to work as well. Install runs fine, launch eclipse and there are no flex view, perspectives, etc. Tried installing the plugin from the local site and it fails with:
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)
Cannot find a solution where both Match[requiredCapability: osgi.bundle/org.eclipse.debug.ui/[3.4.0,4.0.0)] and Match[requiredCapability: osgi.bundle/org.eclipse.debug.ui/[3.2.0,3.3.0)] can be satisfied.
Unsatisfied dependency: [org.jboss.tools.birt.core 1.0.0.Alpha1] requiredCapability: osgi.bundle/org.eclipse.birt.integration.wtp.ui/0.0.0
Cannot find a solution where both Match[requiredCapability: osgi.bundle/org.eclipse.debug.ui/[3.4.0,4.0.0)] and Match[requiredCapability: osgi.bundle/org.eclipse.debug.ui/[3.2.0,3.3.0)] can be satisfied.
Cannot find a solution where both Match[requiredCapability: osgi.bundle/org.eclipse.debug.ui/[3.4.0,4.0.0)] and Match[requiredCapability: osgi.bundle/org.eclipse.debug.ui/[3.2.0,3.3.0)] can be satisfied.
Cannot find a solution where both Match[requiredCapability: osgi.bundle/org.eclipse.debug.ui/[3.4.0,4.0.0)] and Match[requiredCapability: osgi.bundle/org.eclipse.debug.ui/[3.2.0,3.3.0)] can be satisfied.
Cannot find a solution where both Match[requiredCapability: osgi.bundle/org.eclipse.debug.ui/[3.4.0,4.0.0)] and Match[requiredCapability: osgi.bundle/org.eclipse.debug.ui/[3.2.0,3.3.0)] can be satisfied.
Cannot find a solution where both Match[requiredCapability: osgi.bundle/org.eclipse.debug.ui/[3.4.0,4.0.0)] and Match[requiredCapability: osgi.bundle/org.eclipse.debug.ui/[3.2.0,3.3.0)] can be satisfied.
Unsatisfied dependency: [org.eclipse.cdt.debug.gdbjtag.feature.group 5.0.0.200806171202] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.cdt.gnu.debug.feature.group/[5.0.0,6.0.0)
Unsatisfied dependency: [com.adobe.flexbuilder.feature.core.feature.group 3.0.205647] requiredCapability: org.eclipse.equinox.p2.iu/com.adobe.flexbuilder.debug.e32/[3.0.205647,3.0.205647]
Unsatisfied dependency: [org.eclipse.cdt.sdk.feature.group 5.0.0.200806171202] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.cdt.feature.group/[5.0.0,6.0.0)
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: [org.eclipse.cdt.gnu.debug.feature.group 5.0.0.200806171202] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.cdt.debug.mi.core/[5.0.0.200806171202,5.0.0.200806171202]
Unsatisfied dependency: [com.adobe.flexbuilder.feature.core.nl1.feature.group 3.0.205647] requiredCapability: org.eclipse.equinox.p2.iu/com.adobe.flexbuilder.feature.core.feature.group/[3.0.205647,3.0.205647]
Unsatisfied dependency: [org.eclipse.cdt.platform.feature.group 5.0.0.200806171202] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.cdt.core/[5.0.0.200806171202,5.0.0.200806171202]
Unsatisfied dependency: [org.eclipse.cdt.platform.feature.group 5.0.0.200806171202] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.cdt.ui/[5.0.0.200806171202,5.0.0.200806171202]
Unsatisfied dependency: [org.eclipse.cdt.platform.feature.group 5.0.0.200806171202] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.cdt.managedbuilder.core/[5.0.0.200806171202,5.0.0.200806171202]
Unsatisfied dependency: [org.eclipse.cdt.platform.feature.group 5.0.0.200806171202] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.cdt.make.core/[5.0.0.200806171202,5.0.0.200806171202]
Unsatisfied dependency: [org.eclipse.cdt.platform.feature.group 5.0.0.200806171202] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.cdt.debug.core/[5.0.0.200806171202,5.0.0.200806171202]
Unsatisfied dependency: [org.eclipse.cdt.feature.group 5.0.0.200806171202] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.cdt.gnu.debug.feature.group/[5.0.0.200806171202,5.0.0.200806171202]
Unsatisfied dependency: [org.eclipse.cdt.feature.group 5.0.0.200806171202] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.cdt.platform.feature.group/[5.0.0.200806171202,5.0.0.200806171202]
Unsatisfied dependency: [org.jboss.tools.birt.core 1.0.0.Alpha1] requiredCapability: osgi.bundle/org.eclipse.birt.integration.wtp.ui/0.0.0
Unsatisfied dependency: [org.jboss.tools.birt.feature.feature.group 1.0.0.Alpha1] requiredCapability: org.eclipse.equinox.p2.iu/org.jboss.tools.birt.core/[1.0.0.Alpha1,1.0.0.Alpha1]
One thing that I find curious is the flexbuilder package that was supposed to support ganymede was 3.0.1, and this looks like 3.0.205647. Perhaps a bug has crept back in between releases.
I was able to get it installed now. Please view my screencast here: 01 – Installing Eclipse 3.4 (Ganymede) and Flex Builder 3
http://www.red5.org/projects/red5plugin/screencasts/01-Installing_eclipse_and_flexbuilder3.swf
For those of you who successfully installed FB 3.01 and Ganymede, were you installing into Eclipse 3.4.0 or 3.4.1
I am having this same (dependancy) issue above when trying to install FB 3.0.1 into Eclipse 3.4.1
To the original poster, did you get this resolved?
yes, view my screencast to see how i did it: http://www.red5.org/projects/red5plugin/screencasts/01-Installing_eclipse_and_flexbuilder3.swf
Yeah I went through the exact same steps as in your video 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 ———————————————–
eclipse.buildId=M20080911-1700
java.version=1.5.0_16
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)
As I read in the adobe site, the only ganymede version supported is for OS-X, Windows/Unix versions do not work.
@borf, you might want to try one more thing. Restart your machine and try the steps again. don’t install the coldfusion extensions or the js extensions either. Sorry your having trouble.
I had the exact same problem as Borf on OSX. The fix was:
cd /System/Library/Frameworks/JavaVM.framework/Versions/
rm CurrentJDK
sudo ln -s 1.5.0 CurrentJDK
Background: Even though java -version returned 1.5, I had my CurrentJDK pointing to 1.6.0 which appears to play havoc with the FlexBuilder plugin install routine. Once I’d made the symlink for CurrentJDK point to 1.5.0 the installer went fine, and I have FlexBuilder happily running in Eclipse Ganymede 3.4
thanks for your suggestion justin!
I can confirm it is an issue running both 64bit Java 5 and Java 6. I’m assuming as per usual adobe have not properly tested their product and left it up to end users to do it for them for free even though this product isn’t
Goto /Applications/Utilities/Java/Java Preferences
change the order of both to java 5 32bit.
It worked for the jee installation, but it still wont install in my current eclipse installation already with plugins.
Now having to redo for the 50th time a clean eclipse install, and reinstall all my plugins, there is always a plugin that wants to be installed first and its always the last to be installed, its madness.
This is not right, the gui of the mxml does not work I get
Could not open the editor: Assertion failed:
This has taken too long, back to running two versions of eclipse usually at the same time !
Huge time waster, get the 4GB of ram to run two eclipse’s at once stick with standalone flex builder in my opinion. Very annoying hacky untested software.
Hi there-
I just wanted to throw out another solution which virtually eliminates any issues with the installation. It’s definitely something Adobe should resolve soon, but this workaround will get the job done.
http://bugs.adobe.com/jira/browse/FB-13214#action_217678
Good night and good luck,
Thomas
[...] story short: 3 hours later, I found out what was going wrong on Dominick Accattato’s blog (do scroll down and read the [...]
[...] story short: 3 hours later, I found out what was going wrong on Dominick Accattato’s blog (do scroll down and read the [...]
Is it just me or do you really lose around 250 MB disk space after each failed install of this FB3 Plugin (and that’s after removing the directory from /Applications)? Does anybody know where all this stuff is? BTW: It’s good to hear that I’m not the only one with the exact same problem, sad to see that Adobe didn’t make any attempt to fix this. Thanks!
Chris, no I didn’t know that 250MB is lost after each failed install. However, it only goes in two places. 1. It installs in the Applications directory under “Adobe Flex Builder 3 Plug-in”. 2. in the eclipse distribution that you chose to install it into.
You can install FB3 into Ganymeade by using the “links” folder in Eclipse.
1) create a folder in the Eclipse directory named “links”
2) create a file called “com.adobe.flexbuilder.feature.core.link” containing “path=C:/Program Files (x86)/Adobe/Flex Builder 3 Plug-in” (without the quotes and change to where you installed the FB3 plugin
3) restart Eclipse
4) correct the paths to the Flex SDKs under the Window|Preferences|Flex|Installed Flex SDKs
I used this approach using the latest Ganymede and FB3.02 on Windows Vista 64bit.
I ended up using eclipse v. 3.3 and it worked just fine for me. Would not work with the installer for 3.4. Someone else try this and maybe they’ll find it to be true as well? Not sure