Bug#576293: eclipse: plugins installed by user not working
gonzalob at gonz0.com.ar
Fri Apr 2 15:33:01 UTC 2010
After a clean install of eclipse from sid, removing ~/.eclipse and
creating a new workspace, I installed plugins for Maven, Spring
and Subversion, but neither of them were usable after installation.
Thinking it might be a plugin failure, I tried to install PDT. Same thing.
I started eclipse with -debug, -console and -consoleLog. No stack traces,
no warnings, nothing useful that I can think of. The osgi console does not
show any of those plugins after issuing 'ss'.
Lastly, I downloaded the eclipse tarball from eclipse.org and opened
a new workspace. Installed the Maven plugin and it worked seamlessly.
I've been surfing the web for something related to this, and the only
place I found the exact same problem is http://tinyurl.com/ygobwb8, where
it was fixed by removing p2 as he needed a single, not shared installation.
I'm tagging it as Severity: Important as Java development nowadays is far
more than writing classes and interfaces, and eclipse relies on plugins for
almost everything it does.
Please don't hesitate to contact me if I can be of any assistance. I
honestly ran out of ideas, but not of willingness to get this working.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (900, 'testing'), (800, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash
Versions of packages eclipse depends on:
ii eclipse-jdt 3.5.2-2 Eclipse Java Development Tools (JD
ii eclipse-pde 3.5.2-2 Eclipse Plug-in Development Enviro
eclipse recommends no packages.
eclipse suggests no packages.
-- no debconf information
More information about the pkg-java-maintainers