Linux testing, "build fulldist" initial results

[Joseph Kessselman <ke...@alum.mit.edu>]

Checking that what I'm seeing matches what you folks are seeing:

"build fulldist" reports various warnings, of course:
     Use of '_' as an identifier. "might not be supported in releases 
after 1.8".
     Many warnings about no @return, no @param, no @throws, mostly in 
ExsltDatetime.java
     A few scattered advisories about overriding deprecated APIs, or 
using unchecked or unsafe operations.
Eventually it would be nice to have these cleaned up so we get a 
genuinely clean compile.

During the autodocs: stage, I am seeing an error which I am guessing is 
because I'm building under openjdk rather than under the Sun/Oracle 
"product" JDK:
      [java] [Xalan2Processor] Applying XSL sheet 
"sbk:/style/stylesheets/context2label.xsl"
      [java] Exception in thread "main" java.lang.NoClassDefFoundError: 
com/sun/image/codec/jpeg/JPEGCodec
      [java]     at 
org.apache.stylebook.printers.ImagePrinter.print(Unknown Source)
      [java]     at org.apache.stylebook.BasicEntry.create(Unknown Source)
      [java]     at org.apache.stylebook.Project.create(Unknown Source)
      [java]     at org.apache.stylebook.StyleBook.main(Unknown Source)
      [java] Caused by: java.lang.ClassNotFoundException: 
com.sun.image.codec.jpeg.JPEGCodec
      [java]     at 
java.net.URLClassLoader.findClass(URLClassLoader.java:387)
      [java]     at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
      [java]     at 
sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352)
      [java]     at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
      [java]     ... 4 more
      [java] Java Result: 1
We may want to think about whether we need to explicitly require the 
product JDK, or document that this error occurs, or remove the 
dependency on JPEGCoded.

In the autojavadocs-1.4-or-higher: stage,  I'm seeing many warnings 
about missing @throws, @param, @return, along with "no description for 
@throws", plus some errors in the embedded HTML (an instance of <code> 
where </code> was expected seems to be the main cause of that.) Also 
some unexpected end tags, unexpected <KBD>, and other errors. There are 
other instances of malformed XML or stylistically-questionable HTML 
later in the doc phases. This doesn't affect code functionality per se, 
but we should clean it up.

There are places where code is complaining about
     [javadoc] 
/mnt/c/Users/keshlam/xalan/xalan-java/src/javax/xml/validation/SchemaFactory.java:434: 
error: bad use of '>'
     [javadoc]      * this includes files <tt>&lt;include></tt>d or 
<tt>&lt;import></tt>ed,
I seem to remember that un-escaped > is supposed to be permitted (it's 
been many years!), but even if so changing that to balance &lt; and &gt; 
would eliminate the message and be better stylistically.