I liked this idea. So we will have a new method overriding the Object
method and just by that all the code will start using this new method,
instead of the old deprecated one. This will be code change directly only
in one place and indirectly call changed in many places.
If there is a proper
getDeclaredConstructor() will find non-public constructors - that is not a
1:1 replacement.
I wouldn't litter the codebase with code to do all the needed checks if you
replaced it - rather add a " newInstance(Class, ClassLoader)" method
somewhere.
-Tim
On Fri, Mar 29, 2019 at 3:44 PM Brad
You compiled some of it with a newer JDK's javac (or source level), and
some with an older one. My guess is you started a build, some of the
tooling got compiled, then in failed with an error about the JDK being too
new, and so you switched JDKs and tried to keep going.
Hmm, OR, you are using a
