Your message dated Fri, 18 Jun 2010 13:44:41 +0200
with message-id <[email protected]>
and subject line Re: eclipse: installing plugins failed due w3c dtd ban.
has caused the Debian Bug report #577779,
regarding eclipse: installing plugins failed due w3c dtd ban.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
577779: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=577779
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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-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
--- End Message ---
--- Begin Message ---
Version: 3.5.2-2+b1
Hi
I am closing this bug as fixed in eclipse 3.5.2-2+b1.
To the best of my knowledge the issue was caused by some broken symlinks
that was fixed in that version of eclipse. If you can reproduce this
with eclipse (>= 3.5.2-2+b1) with sat4j (>= 2.1.1-3) please write back.
~Niels
signature.asc
Description: OpenPGP digital signature
--- End Message ---
