Re: handling the deprecations introduced by early access builds 116 and 118 of jdk 9

2016-06-06 Thread Richard Hillegas
Thanks for that response, Stuart. One comment inline... On 5/31/16 5:34 PM, Stuart Marks wrote: On 5/30/16 11:48 AM, Richard Hillegas wrote: Dalibor Topic recommended that I post this feedback on core-libs-dev. This is my feedback after ameliorating the deprecation warnings which surfaced

Re: handling the deprecations introduced by early access builds 116 and 118 of jdk 9

2016-06-03 Thread Stuart Marks
On 6/1/16 4:15 PM, Richard Hillegas wrote: [deprecation warnings] This was the issue which I faced. The Derby community has spent considerable effort on maintaining a clean build, one which doesn't swamp real error indications in a blizzard of diagnostic noise. At the same time, we are

Re: handling the deprecations introduced by early access builds 116 and 118 of jdk 9

2016-05-31 Thread Stuart Marks
On 5/30/16 11:48 AM, Richard Hillegas wrote: Dalibor Topic recommended that I post this feedback on core-libs-dev. This is my feedback after ameliorating the deprecation warnings which surfaced when I compiled and tested Apache Derby with early access builds 116 and 118 of JDK 9. Derby is a

handling the deprecations introduced by early access builds 116 and 118 of jdk 9

2016-05-31 Thread Richard Hillegas
Dalibor Topic recommended that I post this feedback on core-libs-dev. This is my feedback after ameliorating the deprecation warnings which surfaced when I compiled and tested Apache Derby with early access builds 116 and 118 of JDK 9. Derby is a pure Java relational database whose original