tree 104aee35bc33622bc4c30650631d068eca1cf1c0
parent f794018fc5383153848b2853c640019f89a1ce44
author Alexander Kriegisch <Alexander@Kriegisch.name> 1701324712 +0700
committer Alexander Kriegisch <Alexander@Kriegisch.name> 1701324712 +0700

Delete xalan2jdoc.jar

Running javadoc generation with or without it on the stylebook classpath
had absolutely no effect. Comparing javadocs with and without it
revealed that both directory trees were binary identical.

Actually, on JDK 8 the JAR cannot have been working correctly anyway,
because the JAR file contained Java 1.1 class files (major 45), which is
OK. But it also uses several classes which are no longer available in
JDK 8, i.e. the code cannot have been working there. For example, one
class imported was
  com.sun.tools.doclets.IndexBuilder,
which a web search found in JDKs 1.2 and 1.3. In 1.8, there is
  com.sun.tools.doclets.internal.toolkit.util.IndexBuilder,
which might serve a similar purpose, but neither is public API nor the
class referenced by the doclet code. I really think, this is just cruft
that can go away.