eclipse 3.5.1 (Galileo) with ubuntu 9.10 (Karmic) busted! Can not install maven2 plugin! (Or any other plugin)_问答_开发者

I see a lot of stuff online related to fixing buttons that can't be pressed, and fixing network issues with proxies. This seems like a different problem to me, related to jem.util.0.0.0 in the case of maven2 or needed libs for other plugins.

The setup:

Eclipse 3.5.1 (Galileo) installed with apt-get. Ubuntu 9.10 (Karmic Koala) (This is running as a VM, not that is should matter.)

General problem description: Maven2 eclipse plugin installation fails.

Specifically, I can not install maven2 plugin from the eclipse installation flow using this target site: http://m2eclipse.sonatype.o开发者_如何学Crg/sites/m2e/

The maven site is found, installation begins, and then returns this error:

Cannot complete the install because one or more required items could not be found. Software being installed: Maven Integration for Eclipse (Required) 0.10.0.20100209-0800\ (org.maven.ide.eclipse.feature.feature.group 0.10.0.20100209-0800) Missing requirement: Maven Integration for Eclipse (Required) 0.10.0.20100209-0800 (org\ .maven.ide.eclipse.feature.feature.group 0.10.0.20100209-0800) requires 'org.eclipse.jem.\ util 0.0.0' but it could not be found

Official Ubuntu documentation claims eclipse 3.5.1 support, and recommends using the Synaptic Package Manager, and nothing else about any issues.

Does anyone has any insight into this?

I manage to install it, but you need to be sure you do not validate just the m2eclipse site, but also the Galileo or Helios update site.

The P2 mechanism will then download all the dependencies (wst, emf, gef, ...) for you, making the manipulations described by Pascal's answer absolutely not needed.

alt text http://img401.imageshack.us/img401/331/eclipsem2install.png

OK - so I got this to work with the following steps:

From Eclipse Menu > Hep > Install New Software > Work With... Add the following site: Galileo - http://download.eclipse.org/releases/galileo

Now install the following (if not there already):

Eclipse Java EE Developer Tools
Eclipse Platform
Eclipse Web Developer Tools
Eclipse XML Editors and Tools
Eclipse XSL Developer Tools
JavaScript Developer Tools
Rich Ajax Platform SDK

Once that was done, I was able to successfully install Maven through the same process.

I was mainly just fooling around to see if it would work or not. Some of the above may be redundant or not needed by everyone.

Maybe Pascal's answer is more direct and straightforward. Anyway, it is working now.

Thanks!

I can't remember exactly but I think I had to install JEM from Eclipse's Visual Editor udpate site. But I'm not using the packaged version of Eclipse so I can't certify you won't have to install more stuff. Actually, according to this page, you might have to:

I had to jump through quite a few hoops to get m2eclipse installed in Eclipse 3.5.1 on Ubuntu 9.10. I had to install these dependencies in this order:

JEM from Eclipse's VE package => http://update.eclipse.org/tools/ve/updates/1.0/

IBM's ICU4J => http://site.icu-project.org/download

Eclipse WST => http://download.eclipse.org/webtools/updates/ (only org.eclipse.wst.* packages)

before Eclipse would allow me to install m2eclipse. JEM in particular is quite well hidden.

Personally, I don't recommend using the packaged version though (i.e. I prefer to install it manually).

The easiest way to fix this is to use the synaptic package manager to install maven2 before you install m2eclipse using the eclipse installtion manager. So the steps would be:

1) system->administration->synaptic package manager: check maven2 (and all of its dependencies)

2) eclipse->help->install new software: use http://m2eclipse.sonatype.org/sites/m2e and follow the installation directions.

In general when dealing Java tools it's best to install them manually rather than relying on the Linux packaging mechanisms. Java applications typically have their own dependency mechanisms which work better/are better maintained and I find less hassles by not to mixing the two.

The problem is Gnome API changes that blocks some SWT widgets from receiving display events. It was fixed in the Eclipse 3.6 code, for older versions just set environment variable GDK_NATIVE_WINDOWS=true.

I had some trouble when I upgraded to Karmic - the plugin installation dialog was only half-functional. It turned out to be an issue with GDK. There's an easy fix - set GDK_NATIVE_WINDOWS=1 in your environment. http://blog.export.be/2009/10/fixing-eclipse-for-ubuntu-karmic-koala-9-10/