Ok guys we did some research on this and figured out what is going on, here’s the deal:
1. MyEclipse’s integration of Spring IDE includes the Mylyn-extensions of SpringIDE which require Mylyn 2.3
2. If you add Mylyn to your MyEclipse 6.5 profile in Pulse, Pulse will provision the latest compatible version of each piece of software (and in MyEclipse’s profile, we didn’t set a hard-dependency on Mylyn 2.3, so it gets upgraded to Mylyn 3.0)
3. The upgrade to Mylyn 3.0 is what causes all the Spring stuff to throw exceptions and break.
4. Even after removing Mylyn from the MyEclipse Profile, it can still load and still cause the bug.
FIX: Remove Mylyn form your MyEclipse Profile, right-click on the profile and do Reinstall and Run, that will completely remove it and fire the profile back up.
KNOWN ISSUE: You cannot add Mylyn right now, in Pulse, to MyEclipse. We are working on getting all the snaffus mentioned above fixed. Sorry for the trouble guys but thank you for bringing it to our attention, very interesting use case here with some area we can tighten up ASAP.