For some time now, I’ve been using Eclipse with the Flex Builder plug-in to code my Java/Flex projects. Recently I’ve decided to switch from Flex Builder 3 to Flash Builder 4. And since Eclipse Galileo had just been released, I just had to add it to the migration stack and let go of good ol’ Ganymede.
Installing Eclipse Galileo
As usual, installing Eclipse is a breeze. Go to the downloads page, select the package that suits you best, download it, then decompress it. I’ve taken the Java EE package for Mac OS X (Carbon), since it suits best my needs and the platform I’m running on (Mac OS X Leopard 10.5.7).
Installing Flash Builder 4
Download it from the Flash Builder 4 page from Adobe Labs.
Installing Flash Builder 4
Everything went smooth and after the installation was done, I was able to create my first FB4 project :
My first FB4 project
Other plug-ins
After FB4, I did install other plug-ins that I use in my daily work : the Perforce plug-in, M2Eclipse, the TestNG plug-in, JBoss Tools, EclEmma, the PMD plug-in, the Checkstyle plug-in and Flex Formatter.
Everything works fine, just as before, and I’m very pleased about it.
Migrating the workspace
The real test for my new IDE stack was migrating the workspaces I use. After everything was in place, I opened my latest workspace with my new Eclipse and it turned out to be OK. I didn’t experience any issues with the Java projects or the plug-ins.
Migrating Flex projects
Everything worked out smoothly, except for the Flex projects. When building the Flex projects from my workspace, I kept running into an error with a message like this :
Attempted to beginRule: R/, does not match outer scope rule: P/my.project
This error would pop up during each project build, so I had to do something about. I did a bit of googling and it turned out that this message is common to multiple issues to Eclipse, most of them who got fixed, so that didn’t help me much. I tried out a couple of workarounds and in the end I managed to fix the problem by deleting the Flex projects from the workspace (but not the project contents) and then using the Import wizard to recreate them :
Import the Flex project as an existing project
After I did this I didn’t receive any more errors when building the projects. However, I did change the default Flex SDK to be Flex SDK 3.4, instead of 4.0 as Flash Builder defaults to. This was the last configuration I had to do before I could work as smoothly as I did before with the Eclipse Ganymede/Flex Builder 3 stack.
Can I ask what version of OS X you might be running? Also whether you downloaded Cocoa Galileo or Carbon…
Here on Snow Leopard with Cocoa Galileo, Flash Builder does not work at all.
@ Jeroen
I run Galileo Carbon on OS X Leopard 10.5.7 ; I’ve updated the post and included this information as well. On this platform Flash Builder works just fine. What kind of issues are you encountering with FB ?
@ Jeroen
I second that, I used galileo cocoa and the Flex Builder 3 does not launch (haven’t tried 4)
tried it with 4, and it doesn’t work either
@Luis
At this moment the Flash Builder plug-in only works on the Carbon version of Galileo.
Hi
currently i am using Flexbuilder3 IDE .already flex 3 is installed in my system.can i install flash builder 4 also in the same operating system?will it make any problem?whether i need to uninstall my flexbuilder 3?.Please let me know comments.I am using windows 7 as operating system.
Thanks
Ganesh
Hi,
I follow the entire step what is mentioned here. I m trying to make the flash builder to licensed. After installation i am not getting any pup up to give my serial number. Can u help me how I can make it licensed?
Thanks,
Satya
satyalok, try reinstalling from scratch