Assume that means bumping commons compress to 1.21 then? Where does this external dependency and its version get defined?
Where would this sort of unpack usage occur in the code base? Assume the test for this would be point to legacy plug-in and try to install, assuming either version of Java when pack/unpack not available and verify the plug-in installs? On Tue, Jul 20, 2021 at 9:57 AM Neil C Smith <[email protected]> wrote: > On Fri, 26 Mar 2021 at 14:14, Eric Bresie <[email protected]> wrote: > > The IDE/Platform is updated/updating to newer Java it’s how to handle > the legacy plug-ins that I’m concerned about > > > > Its the independent plugins which leverages pack 200 / unpack during > plug-in install. > > Just reading the changelog for Commons Compress (for another reason) > and noticed that pack200 support was included in the last release this > month. https://commons.apache.org/proper/commons-compress/ > > Best wishes, > > Neil > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > > -- Eric Bresie [email protected]
