Eclipse (3.4) will not load Flex Plugin - apache-flex

I installed Flex Builder plug in (3.2) into Eclipse 3.4. The installation had no errors, but I get this error when trying to start a new Flex Project.
The selected wizard could not be started.
Plug-in com.adobe.flexbuilder.apollo.ui was unable to load class com.adobe.flexbuilder.apollo.ui.wizards.flex.FlexApolloProjectWizard.
com/adobe/flexbuilder/editors/common/ui/project/wizards/AbstractFlexProjectWizar d
I have tried re-installing several times, even tried the older eclipse versions.
Any thoughts ?

When Flex is installed on a Windows machine, it generates two versions of the Flex SDK, one in C:/Programs Files/Adobe/Flex Builder 3 Plug-in and the other in your Eclipse directory (not sure if this is true on a Mac). I've fixed similar issues by copying missing files from the Flex Builder folder into the parallel Eclipse plug-in directory. That would be my first guess.
If that does not work, you may have to contact Adobe.
Sometimes Flex is... terrible. I mean absolutely awful.

There was a major kerfluful with the fact that FlexBuilder would install correctly in Eclipse 3.4. The new Flashbuilder, for version 4 is designed to work with 3.5(galileo), I'm hoping that it will work with Helios, so I will no longer need to keep multiple Eclipse versions going. Here's a link on how to make it work. I just hope we don't have to keep repeating this.

Related

FlexVersion compatibility has already been read - _NOT_ Flex 3 to Flex 4 issue

To be clear, this code was working for many years using Flex 4.5.1. As such, this is not answered by; Error migrating Flex 3 to Flex 4
I am bulk generating Font CSS SWF in Flash Builder. There are nearly 700 of them, so I cannot do it in my main project, but have a related project to do so. Both projects are compiled using the same SDK (I have tried 4.6.0 (Adobe), 4.12.0 (Apache Flex), 4.13.0 (Apache Flex)).
However, since upgrading to 4.6+ from 4.5.1, I can no longer import fonts on demand as they immediately trigger Error: Compatibility version has already been read. error on load.
Can anybody direct me to a workaround for this? Or explain what causes compatibility version to be written on load of SWF?
See my comment above. This was resolved to inconsistent SDK in a complex build environment. Once everything matched (exactly) the issue disappeared.

Adobe Flex Development on Ubuntu

I'm thinking the following:
Netbeans + FlexBeans
Maven + FlexMojos
However:
FlexBeans just doesn't compare with FlexBuilder
Not sure FlexMojos supports Flex 4
How do you guys manage to develop Flex apps on Ubuntu?
I personally prefer Netbeans to Eclipse. Netbeans has very good Maven project support. So I am thinking of:
"Extending" FlexMojos to work with Flex 4
Forking or developing from scratch a good Flex plugin for Netbeans\
Any ideas?
I've been developing with Flex on Ubuntu for the last 6 months with IntelliJ IDEA 9.
Besides many interesting features (that Flex Builder 3 does not have), the editor supports Maven and FlexMojos nicely. You can actually just import your poms directly into IDEA and it will create all configurations for you. This is also interesting if you are using a build server that uses Maven so you don't have to maintain multiple build configurations.
IntelliJ IDEA: http://www.jetbrains.com/idea/
FlexMojos: http://code.google.com/p/flex-mojos/
Give a go to FDT, they've just added MXML support. It's not cheap by any means, but worth trying.
Cheers, J
However:
* Not sure FlexMojos supports Flex 4
http://flexmojos.sonatype.org/
Adobe is working on a Linux version of Flex Builder.
SapphireSteel has a plugin for Visual Studio called Amethyst
Ensemble has another one called Tofino
I develop Flex apps that run on Linux. I run VMWare on Centos and run Vista on that and have FlexBuilder installed in the virtual machine. It works pretty well since I found the Linux FlexBuilder to be very buggy and I can still use Linux for everything else.
There is an unsanctioned project to get Flash Builder 4 to run on Linux. I have tried it out and it works very well. The only real missing feature is design mode.
http://code.google.com/p/fb4linux/

Does FlexBuilder 3 work with Eclipse 3.5.1?

I m trying to install Flex Builder 3 into Eclipse 3.5.1 as a plugin on Mac 10.6.2.
During the installation phase, FB3 says it only support eclipse 3.3 & 3.4. But I started the installation anyway.
After the installation was done, I can't find Flex perspective from Eclipse. So I google around and found out the possible way to manually add this link file from folder "links" to point to the FB3 Plugin folder. I did that and FB perspective can be shown now. But when I try to switch to FB perspective, error occurs:
Problems opening perspective:
'com.adobe.flexbuilder.editors.mxml.ui.perspectives.development'
Anyone has done this successfully?
Unfortunately Eclipse 3.5 is unsupported by Flex Builder 3. There are a few bugs for this:
http://bugs.adobe.com/jira/browse/FB-21025
http://bugs.adobe.com/jira/browse/FB-21284
Please comment on those bugs and vote for them.
I've created a work-around for one of the major issues related to displaying problems.

Flex intellisense forgets flash.*

I am using Eclipse 3.3.2 with the Flex Builder Plugin (3.0.194161) and the Flex SDK 3.2. Recently the intellisense has started forgetting about everything in the flash.* package EXCEPT flash.errors.*
The code still compiles, but attempting to automatically resolve something (CTRL+SPACE) removes any of the flash.* import statements and thus causes a compile error. As it stands I have to either not use CTRL+SPACE, or re-add my flash.* before compiling.
I have tried recreating the workspace/project and have re-installed the Flex SDK, but I still get the same problem.
Any thoughts?
I was able to work around the problem by adding the following SWC to my library path: FLEX_SDK\libs\player\10\playerglobal.swc
It looks like the problem is caused by {targetPlayerMajorVersion} no longer resolving, though I have no idea how that happened.
Edit: Known bug, as described in FB-16703 and "Targeting Flash Player 10"
Upgrade to Flex Builder 3.0.2. I've noticed that older versions of Flex Builder don't like Flash Player 10's new playerglobal.swc.

Could not open the editor: Assertion failed:

when i open .mxml flex file in eclipse it gives error
Could not open the editor: Assertion failed:
Does any one know about it
First of all you can give which operating System and version, IDE version, Flex plugin version, detail of error message. You can try ;
Check eclipse and flex plugin version compatibility if you use flex plugin. (If you use Linux operating system flex plugin compatible with eclipse 3.3 ide if not You can try to install flex plugin on eclipse 3.3 if you use 3.4 or 3.5 and so on)
You can download full package of flex ide instead of flex plugin on eclipse
I think its better to stop searching when you are in Flash and Linux. Here in this link its very much transparent. I tried all the fix provided out there, nothing did really worked what new comers are looking for.
Details: http://labs.adobe.com/technologies/flex/flexbuilder_linux/releasenotes.html#sysreq
Note: GUI will never work, which we are thinking and Autocomplete etc will also not work. So Flash and Linux is actually useless and time lose. The best thing is keep reporting Adobe for this. Because they are counting our Linux Vote.
Try changing your current workspace to another one, it helped in my case.
If you have disabled asking for workspace at startup you can change it here:
Window > Preferences > General > Startup and Shutdown
I just got the same error, after moving my project to a new computer. Turns out the build paths needed to be changed in the new computer. After updating those it seemed to fix the problem.
I struggled with this a couple of hours: my own "solution" to this was that I had Eclipse Galilieo / Weblogic 10.3.2 / Windows 7 set up correctly, but was accidently opening an old Eclipse Helios install pointed to the same projects. In other words yes, its likely a slight path difference or a new name for an updated resource along one of your paths. "assertion failed" is such a generic exception that you could get with so many different softwares, that I thought this input wouldnt hurt...

Resources