3 ms·
> Changing the thrown exception is an incompatible change in Java. Not if you're throwing a more specific exception. So the second and third methods are compat
by tsimionescu 7y ago
> Changing the thrown exception is an incompatible change in Java.
Not if you're throwing a more specific exception. So the second and third methods are compatible with the first one, but not the other way around.
> The vast majority of Java code runs on perfectly well in Android.
The vast majority of Java applications use features not available on Dalvik, ever-changing though the vast majority of their code would indeed run.
> This is what they did. Oracle's argument is that a clean room implementation of the Java API is also copyright infringement.
They did a clean-room implementation by looking at the specification of the Java API. They did not reverse-engineer the API from working programs or from decompiled binaries, and are not claiming that they did. If they had, you would have probably seen minor differences in parameter names, thrown exceptions and a few other places.
- jayd16 7y ago>Not if you're throwing a more specific exception. So the second and third methods are compatible with the first one, but not the other way around. These are public classes and third party code will have overridden the original exception and not your subtype. This would break compatibility. You cannot change the types of these signatures in either direction.