My last checkin (1834841) makes our javadoc targets generate module-aware documentation. Hopefully, this will help stabilize the Jenkins build/test cycle.

I took the liberty of folding the testing javadoc into the same output as the product javadoc. Module-awareness makes it easy to spot which component contains a class.


I have noticed two remaining defects in the javadoc. These may have been introduced by this conversion. But they may have been caused by other work involved in upgrading the Derby build to support Java 9. DERBY-6980 tracks these defects:

1) The public API javadoc does not hot-link to referenced classes in the JDK.

2) The taglet output looks weird. This may be an old problem left over from converting the build to use Java 9 (DERBY-6856).

Please let me know about other problems which you see in the javadoc.

Thanks,
-Rick

Reply via email to