I agree, I am not sure there is a large benefit to changing this at this time. Seems a lot of effort for minimal gain at best.
On Nov 28, 2023, at 12:15 PM, Alan Bateman <alan.bate...@oracle.com<mailto:alan.bate...@oracle.com>> wrote: On 28/11/2023 15:50, Eirik Bjørsnøs wrote: : In light of this, I would like to revisit this issue, 22 years later: - Is my assessment that this change is actually not binary incompatible sound, or did I miss something? - Would it in any case make sense to mark ZipConstants as @Deprecated, maybe for removal to alert people we want to remove the constants? - Could we aim to make the mentioned classes *not* implement ZipConstants, following the regular deprecation process, CSR and release note etc? This is a JDK 1.1 era mistake. It would a source incompatible change to "remove" the constants. It would require corpus searches to gauge the impact. I think the question is whether it's worth the disruption, is your motivation to cleanup this area or something stronger? -Alan [cid:E1C4E2F0-ECD0-4C9D-ADB4-B16CA7BCB7FC@home] Lance Andersen | Principal Member of Technical Staff | +1.781.442.2037 Oracle Java Engineering 1 Network Drive Burlington, MA 01803 lance.ander...@oracle.com<mailto:lance.ander...@oracle.com>
