|
Sort Order:
We've actually successfully installed the plugin with the following combinations: 3.4.2 (from Eclipse.org) and Ubuntu The version in the Ubuntu package manager appears to correspond to 3.5.1 milestone 2. I'll go out on a sturdy limb and say 3.5.1 from Eclipse.org would work. Pretty sure that most Ubuntu folks would rather use the package manager though. Let me know what other information I can provide. Ugggh. These versioning issues are not fun to deal with. I wonder what use is 3.5.1 M2? Another possibility (again, not a solution, but a workaround) is to run software update before installing Groovy-Eclipse so that you are sure to be working with 3.5.1 final, rather than a milestone. I did a "Help" -> "Check for Updates" in Eclipse and a dialog pops up says "There is nothing to update." I'll never pretend to understand Eclipse's Update Manager, but I've never been able to update from a milestone release to a major release through the Update Manager. I've installed the Subversive updates and the m2eclipse plugin, and it seems to like them. I have more interesting info. My "Help" -> "About Eclipse SDK" yields the following information: Version: 3.5.1 And when I go here: http://download.eclipse.org/eclipse/downloads/ It looks like that's the exact timestamp for the version I would download from Eclipse.org! So, it looks like I'm on the blessed version of 3.5.1 from Eclipse.org... conceptually anyway. Interesting...I was going to try to install from 3.5.1M2, but it is not even available any more from eclipse.org. Can you please attach your feature.xml from your jdt feature? eclipse/features/org.eclipse.jdt_<some_garbagy_string>/feature.xml This would let me know exactly what versions you have installed. Thanks. Attached jdt feature.xml from Ubuntu package manager installation For what it's worth, I downloaded the 3.5.1 version from Eclipse and the plug-in installed just fine (as I think we both expected). I am posting to the p2 mailing list. Something odd is going on. The only difference between the feature.xml you sent me and the one for 3.5.1 final is the version of the org.eclipse.jdt branding feature. This should not have any effect on installation. If it helps, the folks that manage the Eclipse distribution for Ubuntu (https://launchpad.net/~eclipse-team Hi guys, I just tried to install the latest Groovy plug-in (from http://dist.springsource.org/milestone/GRECLIPSE/e3.5/ There is a history in why folks on Ubuntu utilize the packaged 3.5.1 version of Eclipse. With the update from Ubuntu 9.04 to 9.10 the Linux guys did improve the GTK version and introduced a "mouse doesn't react as expected" problem (https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/443004 This all should be solved with 3.6.0 - but that's currently not stable enough to work with. Long explanation - but I guess you still don't have a work-around for my installation problem? I ran into the same dependency issue described in this thread ... Best regards, Well, that explains why the 3.5.1 package is different on Ubuntu. And so you are saying that because of bug 443004, it is not possible for you to use the eclipse downloaded directly from eclipse.org? What is happening here, I think is that the patched version of Eclipse on Ubuntu uses a version of the Eclipse platform feature with tight version requirements for the jdt core feature. When Groovy-Eclipse comes along and wants to change that, there is a P2 error because the jdt core feature version needs to change (and the platform feature will not let it). I am not sure of the way around this. Please let me know if this is a blocker for you (ie- downloading from eclipse.org is a bo go) and I will explore more. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Bug
Open
Major
Installation on Eclipse 3.5.1 fails in Ubuntu
Not sure what is going on here.
Could you try downloading Eclipse directly from Eclipse.org instead of using the package manager?
Your jdt.core feature version is different from the one shipped with Eclipse 3.5.1. This really /shouldn't/ make a difference, but this might be a problem.