Preserving API's when removing implementations

[Ron Pressler]

Can you explain the use-case? If the code is still maintained, then it can be changed. If it isn’t maintained
then you’re opting to run unmaintained software and you might as well ship it with an unmaintained runtime.

Sounds like you want to update the runtime but not the software it runs. Why?

— Ron

> On 1 May 2021, at 03:43, Peter Firmstone <peter.firmstone at zeus.net.au> wrote:
> 
> One trend I am noticing as features are removed from Java, is that API that client code utilises is also removed, which prevents other implementations from replacing lost features, where the Java development community needs to continue supporting such features, it breaks software that would otherwise continue to function with an alternative implementation.
> 
> Can we do something about preserving parts of these API's perhaps as deprecated without their removal please?
> 
> Perhaps include the API's in a separate compatibility module, these shouldn't require further development and maintenance, they are just there for backward compatible evolution of client code.
> 
> Thank you.
> 
> -- 
> Regards,
> Peter Firmstone
> Zeus Project Services Pty Ltd.
>