db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4761) javadoc warnings for 10.3 after upgrading to newer (sun) jdk
Date Wed, 04 Aug 2010 13:10:16 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12895239#action_12895239

Rick Hillegas commented on DERBY-4761:

Hi Myrna,

The build was reworked in later branches but a lot of that work probably wasn't backported
to 10.3. One difference I notice about the derbydocs target is that in the 10.3 branch the
javadoc command takes this extra argument, which doesn't appear in the trunk version:

I think that the old build used multiple javac compilers, depending on the rev level of the
code. The javadoc targets however always use the javadoc tool in your $JAVA_HOME environment.

> javadoc warnings for 10.3 after upgrading to newer (sun) jdk
> ------------------------------------------------------------
>                 Key: DERBY-4761
>                 URL: https://issues.apache.org/jira/browse/DERBY-4761
>             Project: Derby
>          Issue Type: Bug
>          Components: Build tools
>    Affects Versions:
>         Environment: with sun jdk 1.6 u21 b7
>            Reporter: Myrna van Lunteren
>         Attachments: 103_jdk16u21_javadocerrors.txt
> I tried to upgrade from an ancient version of the sun jdk to 1.6 u21 b7, but now my javadoc
build for 10.3 ( has a number of errors re 'generics' usage:
> java\engine\org\apache\derby\iapi\jdbc\BrokeredCallableStatement40.java:303: generics
> not supported in -source 1.4
>   [javadoc] (use -source 5 or higher to enable generics)
>   [javadoc]     public <T> T unwrap(java.lang.Class<T> interfaces) 
>   [javadoc]            ^
> etc.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message