Re: Mechanism to maintain backwards compatibility when moving classes to different packages

2019-07-02 Thread Scott Palmer
Friendly reminder :) > -- Forwarded message - > From: Jacob Glickman > Date: Sat, Jun 22, 2019 at 4:42 PM > Subject: Mechanism to maintain backwards compatibility when moving classes > to different packages > To: > > > Yesterday, Mark Reinhold intro

Fwd: Mechanism to maintain backwards compatibility when moving classes to different packages

2019-07-02 Thread Jacob Glickman
Friendly reminder :) -- Forwarded message - From: Jacob Glickman Date: Sat, Jun 22, 2019 at 4:42 PM Subject: Mechanism to maintain backwards compatibility when moving classes to different packages To: Yesterday, Mark Reinhold introduced the idea of a java.util.random subpackage

Mechanism to maintain backwards compatibility when moving classes to different packages

2019-06-22 Thread Jacob Glickman
Yesterday, Mark Reinhold introduced the idea of a java.util.random subpackage[1]. Obviously, moving java.util.Random into that subpackage is not currently an option, as that would break backwards compatibility. Assuming the subpackage is created, it would make sense to ultimately move java.util.Ran