Bug#576293: eclipse: plugins installed by user not working

[Niels Thykier]

Hi

Is this still a problem in 3.5.2-2+b1?

~Niels




__
This is the maintainer address of Debian's Java team
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers. Please 
use
debian-j...@lists.debian.org for discussions and questions.

Bug#576293: eclipse: plugins installed by user not working

[Micha vor dem Berge]

I also tried to install subclipse the last days and failed. I posted on
the german debian-user list and got the hint to try out subversive (a
different svn-plugin for eclipse). Believe it or not, it works like a
charme. I also tried to install plugins like cdt, pydev and a
blackfin-toolchain. All these plugins work out of the box with eclipse
3.5.2-2 (squeeze) if you install them regular in eclipse. 
For example-plugins that work for me see heading 'Blackfin Plugins' on
http://docs.blackfin.uclinux.org/doku.php?id=toolchain:eclipse:install
for details.
Obviously it must be a plugin-specific bug which affects several but not
all plugins.

Cheers,
Micha vor dem Berge




__
This is the maintainer address of Debian's Java team
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers. Please 
use
debian-j...@lists.debian.org for discussions and questions.

Bug#576293: eclipse: plugins installed by user not working

[Gonzalo Bermúdez]

Package: eclipse
Version: 3.5.2-2
Severity: important

After a clean install of eclipse from sid, removing ~/.eclipse and 
creating a new workspace, I installed plugins for Maven[1], Spring[2] 
and Subversion[3], 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.

[1] http://m2eclipse.sonatype.org/installing-m2eclipse.html
[2] http://springide.org/updatesite/site.xml
[3] http://subclipse.tigris.org/update_1.6.x

-- 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-2Eclipse Java Development Tools (JD
ii  eclipse-pde   3.5.2-2Eclipse Plug-in Development Enviro

eclipse recommends no packages.

eclipse suggests no packages.

-- no debconf information



__
This is the maintainer address of Debian's Java team
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers. Please 
use
debian-j...@lists.debian.org for discussions and questions.