Hi,
Since 1/15 I see some new javadoc warnings from my automated build:
Docs:
Failed with following errors. Check details in docs.txt
[javadoc]
<mypathtotrunk>\java\drda\org\apache\derby\impl\drda\DRDAConnThread.java:7534:
warning - @param argument "elemNum" is not a parameter name.
[javadoc] 1 warning
Failed with following errors. Check details in buildZip.txt
[java] SANITY >>>
/org/apache/derby/impl/drda/DDMWriter.class
Does anyone else see these?
This came out of a run where the updates were:
====================
r899819 | rhillegas | 2010-01-15 13:32:14 -0800 (Fri, 15 Jan 2010) | 1 line
DERBY-4491: Fix sealing violation which kills the AssertFailureTest on
runs against insane jar files.
------------------------------------------------------------------------
r899733 | rhillegas | 2010-01-15 09:54:20 -0800 (Fri, 15 Jan 2010) | 1 line
DERBY-4491: Correct the network metadata for UDTs and make it possible
to pass UDT values across the network.
------------------------------------------------------------------------
r899588 | dag | 2010-01-15 02:53:22 -0800 (Fri, 15 Jan 2010) | 11 lines
DERBY-4397 Allow ORDER BY in subqueries
Patch derby-4397-sortavoidance-a, which makes sort avoidance work in
the simple case of a subquery with order by on a base table which has
a suitable index. The fix avoids the result columns assumed by the
order by list from changing after they have been bound, to include a
level of VCNs, which is not correct (this happened as a side effect of
copying result columns from the subquery up to the FromSubquery node).
A new test case the verify sort avoidance in this case has been added.
------------------------------------------------------------------------
r899576 | kristwaa | 2010-01-15 01:49:19 -0800 (Fri, 15 Jan 2010) | 2 lines
Removed unused method SQLChar.readCharacterLength
====================
