I'll fix this. Should I fix it right away or wait - don't want
to cause more problems with applying your patch. Let me know.
Rick Hillegas (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-862?page=comments#action_12364473 ]
Rick Hillegas commented on DERBY-862:
-------------------------------------
Hoopla. The new patch uploaded cleanly. I have successfully downloaded and
applied it to a clean client. In other good news, since I generated this patch
only two new javadoc warnings have crept in:
[javadoc]
C:\cygwin\home\rh161140\derby\mainline\trunk\javadoc\sourcedir\org\apache\derby\impl\store\raw\data\BaseCont
ainer.java:832: warning - @param argument "backupConatainerPath" is not a
parameter name.
[javadoc]
C:\cygwin\home\rh161140\derby\mainline\trunk\javadoc\sourcedir\org\apache\derby\impl\store\raw\data\BaseCont
ainerHandle.java:980: warning - @param argument "backupConatainerPath" is not a
parameter name.
Clean up the big pile of javadoc warnings for the derbydocs target and make
derbydocs run under jdk1.6
------------------------------------------------------------------------------------------------------
Key: DERBY-862
URL: http://issues.apache.org/jira/browse/DERBY-862
Project: Derby
Type: Improvement
Components: Javadoc
Reporter: Rick Hillegas
Assignee: Rick Hillegas
Attachments: bug862.diff, bug862_rev2.diff, clean_javadoc.output,
svn_status.bug862, svn_status_rev2.bug862
Right now, the derbydocs target produces a blizzard of warnings. In addition,
javadoc fails under jdk1.6 because of illegal html in Property.java and ij.jj.
