Thanks for investigating that sample case, Peter, and for providing a
candidate solution. It is much appreciated. Your expert experience
confirms my amateur hunch that this migration is a non-trivial
re-factorization which merits its own mini-project. I have logged a new
technical debt issue to
anel#comment-15990011
Thanks,
-Rick
On 5/4/17 9:48 AM, Lance Andersen wrote:
On May 4, 2017, at 11:32 AM, Mandy Chung wrote:
On May 3, 2017, at 11:16 PM, Peter Levart wrote:
Hi Rick,
Allow me to join the discussion...
On 05/04/2017 04:21 AM, Rick Hillegas wrote:
Thanks, Roger. That is a hel
ce
from becoming unreferences.
If there are more specific cases of interest let me know,
Regards, Roger
On 5/2/2017 10:08 PM, Rick Hillegas wrote:
When I compile Apache Derby using JDK 9 build 167, I see several
instances of the following warning:
warning: [deprecation] finalize() in Ob
When I compile Apache Derby using JDK 9 build 167, I see several
instances of the following warning:
warning: [deprecation] finalize() in Object has been deprecated
The javadoc for java.lang.Object.finalize() suggests that affected
classes should migrate their finalization to a coding patte
