Bug#577779: eclipse: installing plugins failed due w3c dtd ban.
chihchun at kalug.linux.org.tw
Wed Apr 14 16:07:47 UTC 2010
Actually, I found the dtd issue after
I found the plugins stop working.
It happends after I did `aptitude upgrade' today.
I upgraded 113 packages, and most related packages are
xulrunner-1.9.1 18.104.22.168-3 -> 22.214.171.124-5
sat4j 2.1.1-2 -> 2.1.1-3,
ca-certificates-java 20100406 -> 20100412
So, I deleted workspace and ~/.eclipse, and
reinstall the plugins again.
(which suppose menas I did not install any other plugins)
Then I found 503 dtd issue.
You can see the plugins I installed in the previous mail
I was trying to install GWT plugins. GWT depends on
other plugins from eclipses.
So I added two repositories,
There is a related issue in lauchpad.
2010/4/14 Niels Thykier <niels at thykier.net>:
> Hi Rex Tsai
> Your issue looked very different from #576293 (where installing plugins
> was possible, not they were not loaded), so I cloned the report as
> #577779 and set you as submitter of it. If you have any bookmarks or
> subscribed to #576293, you may want to update these.
> As for your 503 problem with the DTDs: Have you installed any eclipse
> plugins except for those obtained via Debian?
> To the best of my knowledge there should not be a XML verifier in part
> of eclipse shipped by Debian and I cannot reproduce the DTD issue myself.
More information about the pkg-java-maintainers