[ 
https://issues.apache.org/jira/browse/DERBY-4761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Myrna van Lunteren updated DERBY-4761:
--------------------------------------

    Attachment: DERBY-4761.diff

I looked at the changes that went in after the 10.3 branch was cut, and as far 
as I can tell, that's when we decided it was no longer needed to build with 
jdk142 compiler. So, I didn't think it appropriate to backport any of those 
changes.

Attaching a patch that fixes these errors for me.

basically it's adding 1 file 'jdbc4list' to the javadoc exclusions, then where 
it's actually doing the javadoc call, I've added a similar section that does 
the javadoc with source=1.5 if jdk16 is  set.

If no comments I'll commit this in a day or so, and I've also found similar 
warnings popped up in my 10.2 build after the upgrade  to a later sun jdk 1.6,  
so I'll investigate backporting  this patch to 10.2.

> 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: 10.3.3.0
>         Environment: with sun jdk 1.6 u21 b7
>            Reporter: Myrna van Lunteren
>         Attachments: 103_jdk16u21_javadocerrors.txt, DERBY-4761.diff
>
>
> 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 (10.3.3.1) has a number of errors re 'generics' 
> usage:
> java\engine\org\apache\derby\iapi\jdbc\BrokeredCallableStatement40.java:303: 
> generics are 
> 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.

Reply via email to