Eclipse 3.4.1 Ganymede, MXUnit, Flexbuilder 3 on MacOSX

After a few minutes of thrashing with a incompatibility issue that was giving me trouble installing MXUnit in Eclipse 3.4.1 I found a work around I thought other people might benefit from.

First the back story. I had Eclipse 3.3 running happily on my Mac with Flex Builder, CFEclipse, SVEclipse, etc... Then I tried to install MXUnit, and I kept running into a incompatibility issue. Oh well I thought, I guess it's an excuse to upgrade to a newer version of Eclipse.

So I downloaded Eclipse 3.4.1 Ganymede and proceed to install all my usual plugins including Flexbuilder (I kept a copy of by 3.3 install just in case though). When I tried to install MXUnit though it again complained about an incompatibility. It looked something like this:

Cannot complete the request. See the details. Cannot find a solution where both Match[requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.equinox.preferences/[3.2.201.R34x_v20080709,3.2.201.R34x_v20080709]] and Match[requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.equinox.preferences/[3.2.200.v20080421-2006,3.2.200.v20080421-2006]] can be satisfied.

I did find something on Google similar to this: http://forum.springframework.org/showthread.php?t=63187 But the solution in that thread was to manually install a pre-release version of equinox which I didn't really feel like messing with.

I looked at the incompatibility message a little closer (I didn't include the whole thing above because it was sooooo loooong) and saw it mentioned Flex Builder which I had already installed successfully. It seemed to suggest that Flex Builder was causing the incompatibility issue.

Just for laughs I decided to try uninstalling Flex Builder and then install MXUnit. SUCCESS! What's more after MXUnit was installed I had no problem installing Flex Builder.

I never would have guessed it, well I suppose I did stumble upon it but I didn't really thing it was going to work. Flex builder must be a little more flexible (ha) in regrards to which version of the equinox plugin is installed.

I wonder if the same workaround would have worked with 3.3, probably. No time to check now though gotta get back to work using shiny new eclipse 3.4.