Thursday, June 25, 2009

Flex Builder 3 on Eclipse 3.5 (Gallileo) on OS X?

I spent a little time this morning trying to get FlexBuilder 3 up and running in Eclipse 3.5 (Gallileo). A little experimentation and reading implied that getting it up in the Cocoa version of Eclipse wasn't going to happen.

I then tried a few more times with Eclipse 3.5 carbon, and still wasn't able to get it working. So if you've managed to get FlexBuilder 3.X up and running on Eclipse 3.5 on OS X, I'd be happy to hear more.

20 comments:

Holger Herzog said...

It seems to be the case that when using the flex builder installer, the plugin dependencies are not checked. At runtime you then get NoClassDefFound errors. The classes are there, but they are not loaded because of two dependency constaints:

com.adobe.datatools.derived needs com.ibm.ecu in an older version as shipped with galileo
com.adobe.flexbuilder.debug.e32 needs org.eclipse.forgottenwhatexactly in an older version as shipped with galileo

I patched the dependency constaints to get the classes loaded. But unfortunatally this resulted in NullPointerException when calculating the decorators in the overview view.

I don't see a further way to run flex builder 3 with eclipse galileo.

dethell said...

Just spent about 30 minutes trying to do this myself and also got nowhere. I'll keep a bookmark here in case someone else figures this out. Sure would be nice for Adobe to add support for Cocoa in a patch to FB3 or in the upcoming FB4, but from the bug reports it looks like they won't be doing it.

Holger Herzog said...

I forgot to say:

When cocoa failed, I tried this with carbon! --> Negative! When compiling the projects, I get the message that an error occured while removing problem markers.

Did anybody get it running: Flex Builder 3 with Galileo Carbon, at least?

I'm tracking this entry, too.

Bill said...

This guy seemed to get it working although he appears to be using Windows. Anyone try this with the Mac version?

Darren said...

I have FB3 working in Gallileo. It only took a couple of minutes. Firstly, yes, you have to use the Carbon version of Gallileo (I actually used the newest Carbon PDT All-in-one). Similar to the Windows instructions linked to by Bill, close Eclipse if it's running and then create a folder called 'links' in your Eclipse app folder. Inside this folder create a file called 'com.adobe.flexbuilder.feature.core.osx.link'. This file contains just one line of text, like so:

path=/Applications/Adobe Flex Builder 3 Plug-in

Start Eclipse and enjoy.

Anonymous said...

I created the link 'com.adobe.flexbuilder.feature.core.osx.link' in the subfolder "dropins" within the eclipse folder. And it works.

ulf

Geoffrey Wiseman said...

Weird; I tried the 'links' folder before posting this, and again now after reading this comment, no dice. Eclipse loads with blank perspectives where Flex used to be. Trying to open .as files does nothin'. It seems to know that FlexBuilder Exists (e.g. in the 'configuration' tab of About Eclipse) but it's as broken as can be, for me.

I wonder why it's different for you?

Darren said...

In my case, I had a working installation of Eclipse 3.4 with Flex Builder installed as a plugin. All I did to upgrade was rename the Eclipse app folder to 'eclipseold' and copy the unzipped Carbon Gallileo 'eclipse' folder into Applications. After reading the post linked to in Bill's comment, I had a look in the 'eclipseold' folder and there was already a 'links' folder there containing com.adobe.flexbuilder.feature.core.osx.link so I just copied the 'links' folder into my eclipse folder. Finally, I had to edit com.adobe.flexbuilder.feature.core.osx.link by adding 'path=' to the beginning of the line of text in that file. That's all I did and I haven't had any issues.

If re-installing Flex Builder into Gallileo doesn't work, you could probably get up and running by uninstalling Flex Builder, installing a fresh copy of Ganymede, installing Flex Builder as a plug-in into that installation and then recreating the steps above.

Geoffrey Wiseman said...

Ah, it was the 'path=' part I was missing. I did notice that difference at one point, but then forgot to make that adjustment later. That seems to have done the trick for me; great.

dethell said...

Well, I thought I had FB working in Galileo Carbon, but I'm getting all kinds of compiler errors like "Removing compilter problem markers" and such. Basically, if there are any true errors in my code it won't find them and won't compile. If I manage to find the offending code and fix it, the compile works (sometimes) but the error about removing compiler problem markers still shows.

Any ideas?

-dethell

Geoffrey Wiseman said...

Yes, I've had the same problem WRT "removing problem markers"; starting from a fresh workspace doesn't seem to help for me, so I've reverted bacy to Ganymede (3.4) for now.

Most of the time, it was compiling and displaying errors correctly, but I was getting very irritated by the constant barrage of pop-ups telling me about the inability to remove problem markers.

Is anyone /not/ experiencing this with FlexBuilder 3.X on Eclipse 3.5?

gabriel said...

Hi All,

As Geoffrey indicates - I too have made the path= change and am getting the compiler marker issue and generally having an unusable experience with the Flex Builder Plug in and 3.5. :(

Stu Thompson said...

I too am in the "no go" club too for OSX/Cocoa/Eclipse3.5/FB3. For now I think I'll run two different versions of Eclipse...one just for FB3 and one for everything else. (Bah, humbug.)

Rodrigo Gómez-Tagle A. said...

I tried as well OSX/Galileo_carbon/FB3_plugin.
Got it to show the perspective no problem with the link folder but when compiling it throws a bunch of errors.
Went back to working with FB3 for now.
Will check later to see if there is news.

Anonymous said...

fyi - I tried the same thing on Windows - i.e., Eclipse Galileo, Flex Builder 3 plugin, using the "links" folder, etc... -- still getting the "Removing compile problem markers" issue

Darren said...

Has anyone tried James Ward's fix for Flex on Galileo?

http://www.insideria.com/2009/09/fixed-an-internal-build-error.html

Joel Saltzman said...

I had a good install, without errors. Here is what I did:

I uninstalled FB Plugin
Deleted my Eclipse folder
Downloaded new Carbon PDT
Extracted
Moved to Applications
Downloaded the new FB Plugin
Reinstalled
Picked my new Eclipse folder
Installer warned me, I continued.

Everything worked fine. No compiler errors, MXML editor works, design view works.

Dejan Inic said...

Has anyone solved this problem so far???

I have seen people solving this problem but only on Windows. If there is anyone that solved this for MAC OS please let me know.

Renee said...

I was able to install James Ward's fix and that got me beyond the compiler errors (using Mac OS X 10.5.8). However, when I create a combined Flex/Java project now, it no longer compiles the Flex portion correctly.

I currently have the two versions set up, both Ganymede and Galileo, with a very simple Java EE test app in each. In Ganymede it works fine, but when I compile and deploy the same exact code to a Glassfish server using Galileo, it does not create the helper files (i.e., the .html, .swf, etc).

My ultimate goal is to move to Java EE 6, so I have to be able to use Galileo. Does anyone have any pointers or suggestions on what the problem might be and any possible fixes?

Thanks so much for any help! I'm really striking out here.

mig said...

So I did what Joel did, downloading the carbon PHP version of 3.5 eclipse, changed the com.adobe file to have path= at the beginning of it, and upgraded to the java tools to get ant (for our extra build widgets).

I'm building my stuff fine, tho we don't use wizards so I can't speak to how those may be working for you all.

mig

Joel Saltzman said...
I had a good install, without errors. Here is what I did:

I uninstalled FB Plugin
Deleted my Eclipse folder
Downloaded new Carbon PDT
Extracted
Moved to Applications
Downloaded the new FB Plugin
Reinstalled
Picked my new Eclipse folder
Installer warned me, I continued.

Everything worked fine. No compiler errors, MXML editor works, design view works.