Mike Potter

July 6, 2006

Flex and Eclipse 3.2?

I picked up a copy of my local newspaper this morning, flipped to the tech section and lo and behold, there's a quote from my boss about Eclipse 3.2.

Well, since I have pretty much every program that's available to be downloaded installed (and in many cases, uninstalled shortly thereafter) on my machine, I thought I'd see what Flex Builder 2 and Eclipse 3.2 looked like together.

Note: Flex 2 requires Eclipse 3.1.1/2, as mentioned on the system requirements page.  The following is definitely, 100% not supported by Adobe.  Follow along at your own risk.

First, I downloaded Eclipse 3.2, then I downloaded the free trial of Flex Builder 2 from Adobe's website.  I installed the plug-in version of Flex Builder into the Eclipse 3.2 directory (c:\eclipse32 for me)... I then ran Eclipse 3.2 and received a few errors.  Nothing major, so a few clicks on "OK" and we're off and running... The code view appears to work fine, with code hinting and code completion working.  Compiling an application went fine as well, I compiled a few of the older projects I had in my workspace, no problems.

(Have I mentioned that Flex Builder 2 is definitely unsupported on Eclipse 3.2?)

Debugging, well that was another story.  If you debug applications often, then you'll want to stick with Eclipse 3.1.1 or 3.1.2 for now.  In my (short) test period, debugging didn't work.

So, there's still some work to do.  If you want to try it out on your own, you can download Eclipse 3.2 from their website, and install the Flex Builder plug-in version into that folder.  (Warning, its not supported by Adobe, in case you didn't know.)  Just one warning: If you install Flex Builder plug-in for Eclipse 3.2 after you've installed the FB plug-in for 3.1.1/2, then the installer will overwrite your launch shortcut in Start -> All Programs -> Adobe.  You'll need to launch the old version of Eclipse using Start -> Run and entering a path to Eclipse 3.1.1/2.  Oh, and you can't run Eclipse 3.2 and Eclipse 3.1 at the same time.

One final note: Adobe Flex Builder on Eclipse 3.2 is not official supported.

technorati tags:, , ,

Blogged with Flock

Posted by at 10:48 AM on July 6, 2006

Comments

Jim — 11:50 AM on July 6, 2006

Thanks for the info! I've been trying the CFEclipse beta which uses 3.2 and I want to try Flex as well so I'll have to run another install - hopefully things will sync up here shortly and we can use both :)

Bo — 3:06 AM on August 22, 2006

I used Eclipse 3.2 and Flex Builder Plug-in for 1 week ago, and I don't have any problem with installation, first start, and code editing.
BUT, the main problem is when you start the debugger. I can't say "It doesn't work", but some boring errors appears when the debug view try to add the "grey" label that represent a method without sources ...
Else I love Eclipse 3.2 and it's quite good to use the new JDT Package Explorer (with working set management) in Flex Development Perspective ...

My dream is to have an update of the FB to work with E3.2 !!

Nick — 12:39 AM on August 25, 2006

I just installed full version of Flex Builder 2 into an Eclipse 3.2 install and design mode does not work - displays about a hundred "an unknown error has occured" dialogues before returning to the text editor. The demo version of FB2 works fine with Eclipse 3.2, but it seems the full version does not.

Nathanael — 9:21 AM on September 14, 2006

Do you know if Adobe is planning to make flex 2 work with 3.2?

Alberto Gonzalez — 5:51 PM on October 16, 2006

Hi Mike Potter :D

Well, I've been working with the Flex Builder plug-in in Eclipse 3.2 and I haven't had any troubles, even in the debug perspective. I can debug without troubles although I've received a lot of complaints about Callisto and Flex Builder 2.

Dennis Ballance — 2:20 PM on December 14, 2006

Any new word on this? Is Eclipse 3.2 plugin support in the works? Flex looks really attractive, but I'm not willing to step back to 3.1.x to try it out... Thanks!
--Dennis
[After a few months of usage, I can correct myself and say that you actually can debug applications with 3.2. Sometimes I had problems switching from design view to code view and back, but a quick click over to another MXML file solved those problems - Mike]

Thank you for signing in, You may now comment. (Sign Out)

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

Add your comments

Remember Me?

(You may use HTML tags for style.)