db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rick Hillegas <rick.hille...@oracle.com>
Subject Re: odd javadoc output since Friday, Feb 7, 2013
Date Tue, 12 Feb 2013 15:37:22 GMT
Thanks for noticing this, Myrna. As Kristian noted, these warnings are 
caused by the fact that the Java 7 javadoc tool can't find new Java 8 
classes in java.sql. Those classes are referenced by the JDBC 4.2 
support added by DERBY-6000. I have checked in 
derby-6000-13-aa-fixJavadoc.diff at subversion revision 1445196. That 
fixes the javadoc build for me on Java 7.

Note that the javadoc does not build cleanly on Java 8. It spews pages 
of warnings about missing @param and @throws annotations. I think that 
is a separate problem which I will need to tackle later on.

Thanks,
-Rick

On 2/11/13 12:06 PM, Myrna van Lunteren wrote:
> Hi,
>
> Since Friday, I see some unusual output in the javadoc, it doesn't
> seem to be flagging as a warning or error...Does anyone recognize
> this?
>
> ------------------
>   ...
>    [javadoc] Loading source files for package org.apache.derby.impl.jdbc...
>    [javadoc] Constructing Javadoc information...
>    [javadoc] C:\derby\trunk\java\testing\org\apache\derbyTesting\functionTests\tests\jdbc4\PreparedStatementTest42.java:28:
> cannot find symbol
>    [javadoc] symbol  : class JDBCType
>    [javadoc] location: package java.sql
>    [javadoc] import java.sql.JDBCType;
>    [javadoc]                ^
>    [javadoc] C:\derby\trunk\java\testing\org\apache\derbyTesting\functionTests\tests\jdbc4\PreparedStatementTest42.java:59:
> cannot find symbol
>    [javadoc] symbol  : class JDBCType
>    [javadoc] location: class
> org.apache.derbyTesting.functionTests.tests.jdbc4.PreparedStatementTest42
>    [javadoc]     private static  final   JDBCType[]  ILLEGAL_JDBC_TYPES
> = new JDBCType[]
>    [javadoc]                             ^
> (there's more like this)
>
> This started with build at revision level 1443825, and includes the
> following changes:
>
> ========================
> r1443812 | myrnavl | 2013-02-07 16:51:09 -0800 (Thu, 07 Feb 2013) | 9 lines
>
> DERBY-5977; Run storemore and possibly other store .sql tests in junit
> harness using ScriptTest mechanism
>    Committing patch DERBY-5977_2, which:
>    - adds the StoreScriptsTest, and adds it to store._Suite
>    - modifies the .sql scripts run in it to have fully qualified resources
>    - modifies the canons affected to adjust for running them through the
>      ScriptTest mechanism
>    - removes the now unused properties files
>    - removes the .sql scripts run this way from derbyall's storemore suite.
>
> ------------------------------------------------------------------------
> r1443712 | rhillegas | 2013-02-07 12:39:35 -0800 (Thu, 07 Feb 2013) | 1 line
>
> DERBY-6000: Rename DatabaseMetaData.getMaxLogicalLOBSize() to
> getMaxLogicalLobSize().
> ------------------------------------------------------------------------
> r1443697 | rhillegas | 2013-02-07 12:17:08 -0800 (Thu, 07 Feb 2013) | 1 line
>
> DERBY-6000: Add new PreparedStatement.setObject() overloads introduced
> by JDBC 4.2.
> ------------------------------------------------------------------------
> r1443599 | mamta | 2013-02-07 08:42:55 -0800 (Thu, 07 Feb 2013) | 7 lines
>
> DERBY-6053 (Client should use a prepared statement rather than regular
> statement for Connection.setTransactionIsolation)
>
> Sinnce Connection object is already synchronized, no need to use
> synchronized Hashtable, instead us HashMap.
>
> Also parameterize HashMap object declaration for easier usage and
> tighter type checking by the compiler.
> ========================
>


Mime
View raw message