I second Alan's sentiment. If a helpful utility method is called multiple times from Swing code, it does make sense to make publicly available - chances are it is also useful to the application or third party component developers.
Copying code from Swing has a legal aspect - it probably makes the third party code GPL-d, which is probably not what the stakeholders want. -andy From: client-libs-dev <client-libs-dev-r...@openjdk.org> on behalf of Alan Snyder <javali...@cbfiddle.com> Date: Saturday, 2022/12/10 at 08:48 To: Harshitha Onkar <harshitha.on...@oracle.com> Cc: client-libs-dev@openjdk.org <client-libs-dev@openjdk.org> Subject: Re: RFR: JDK-8294680: Refactor scaled border rendering On Dec 9, 2022, at 10:18 AM, Harshitha Onkar <harshitha.on...@oracle.com<mailto:harshitha.on...@oracle.com>> wrote: Do you have a specific use case in mind? No, but as a developer of a third party LAF and various custom Swing components I have had to duplicate “private” Swing code multiple times, so I would like to encourage the view that Swing is an open set of components and LAFs and that the built in components and LAFs should not be considered special or privileged. For amusement, see the JDK class AquaTabbedPaneCopyFromBasicUI where private Swing code was duplicated by Apple and remains.
