Preserving API's when removing implementations

jini at jini at
Sat May 1 02:47:30 UTC 2021

We are not allowed to distribute such libraries, as they are in the java 
namespace unless that's changed?

On 1/05/2021 12:43 pm, Peter Firmstone 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.
Peter Firmstone
0498 286 363
Zeus Project Services Pty Ltd.

More information about the jdk-dev mailing list