db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rick Hillegas <rick.hille...@gmail.com>
Subject Re: Early Access builds of JDK 8u112 b01, JDK 9 b124 are available on java.net
Date Tue, 19 Jul 2016 01:21:39 GMT
Thanks for that suggestion, Dalibor. I have posted a description of my 
experience to the javadoc list.

Cheers,
-Rick

On 7/18/16, 6:56 AM, dalibor topic wrote:
> Hi Rick,
>
> it's great to hear they you've been able to adjust your code to the 
> new Doclet API in JDK 9! It may be worth posting about it to the 
> corresponding OpenJDK javadoc list, as I assume that others making a 
> similar migration later would benefit from learning from your 
> experiences.
>
> cheers,
> dalibor topic
>
> On 17.07.2016 19:17, Rick Hillegas wrote:
>> Hi Rory,
>>
>> I successfully built and ran the Derby tests with b124 of JDK 9. In
>> order to eliminate Taglet-related deprecation warnings, I had to rework
>> some Taglet implementations to use the JDK 9 visitor pattern. I also had
>> to edit many javadoc comments in order to eliminate deprecation warnings
>> when invoking the b124 javadoc tool. My experience is documented in the
>> trailing comments on https://issues.apache.org/jira/browse/DERBY-6856.
>>
>> Thanks,
>> -Rick
>>
>> On 6/27/16 2:03 AM, Rory O'Donnell wrote:
>>>
>>> Hi Rick,
>>>
>>> Early Access b124 <https://jdk9.java.net/download/> for JDK 9 is
>>> available on java.net, summary of  changes are listed here
>>> <http://www.java.net/download/java/jdk9/changes/jdk-9+120.html>.
>>>
>>> Early Access b123 <https://jdk9.java.net/jigsaw/> (#5178) for JDK 9
>>> with Project Jigsaw is available on java.net, summary of  changes are
>>> listed  here
>>> <http://download.java.net/java/jigsaw/archive/123/binaries/jdk-9+123.html>

>>>
>>>
>>> Early Access b01 <https://jdk8.java.net/download.html> for JDK 8u112
>>> is available on java.net.
>>>
>>> Update to JEP 261 : Module System - email from Mark Reinhold [1]
>>>
>>> - The special ALL-DEFAULT module name, which represents the default
>>> set of root modules for use with the -addmods option [2];
>>> - A more thorough explanation of how the built-in class loaders have
>>> changed, how built-in modules are assigned to each loader,
>>>    and how these loaders work together to load classes [3]; and
>>> - The reason why Java EE-related modules are no longer resolved by
>>> default [4].
>>> - There are various other minor corrections and clarifications, as can
>>> be seen in the detailed diff [5].
>>>
>>>
>>> Rgds,Rory
>>>
>>> [1] 
>>> http://mail.openjdk.java.net/pipermail/jigsaw-dev/2016-June/008227.html
>>> [2] http://openjdk.java.net/jeps/261#ALL-DEFAULT
>>> [3] http://openjdk.java.net/jeps/261#Class-loaders
>>> [4] http://openjdk.java.net/jeps/261#EE-modules
>>> [5] 
>>> http://cr.openjdk.java.net/~mr/jigsaw/jeps/updates/261-2016-06-15.html
>>> <http://cr.openjdk.java.net/%7Emr/jigsaw/jeps/updates/261-2016-06-15.html>

>>>
>>> -- 
>>> Rgds,Rory O'Donnell
>>> Quality Engineering Manager
>>> Oracle EMEA, Dublin,Ireland
>>
>


Mime
View raw message