+1, people on old versions of Java can remain on the old version of the plugin. No one who is in a project where an old version of Java is still in use (< 8) expect to have everything else in their eco-system (3PPs, maven plugins etc) at bleeding edge versions. I guess many such projects are many versions behind on even supported releases...particularly regarding Maven plugins.
- Eric L On Mon, Jun 3, 2019 at 7:23 PM Mickael Istria <mist...@redhat.com> wrote: > People who don't want to update are the ones who have to pay the effort, > not the project that tries to ship a security fix. > The simplest past forward is the one provided by Tony. Customers who don't > want to use it can remain on previous version of the archetype plugins. > Other proposals to fix it are just more time-consuming without providing > value to Maven project. >
