Re: [DISCUSS] MNG-7020 Remove Maven 2 WagonExcluder backward compat code

2021-02-06 Thread Michael Osipov
Am 2021-02-06 um 14:32 schrieb Robert Scholte: (I'm not sure if this has already been discussed on the dev-list, but I can't find any related thread) Plugins that depend on maven-core 2.x will pull in Wagon, which causes unwanted behavior (it will superseed the one bundled with Maven for that

Re: [DISCUSS] MNG-7020 Remove Maven 2 WagonExcluder backward compat code

2021-02-06 Thread Sylwester Lachiewicz
+1 for option 3 sob., 6 lut 2021, 14:43 użytkownik Tamás Cservenák napisał: > +1 fot option 3: we drag so much of legacy, that m4 really should accept > maven 3.1+ plugins only (covers 14 years?). > > T > > On Sat, Feb 6, 2021, 14:32 Robert Scholte wrote: > > > (I'm not sure if this has already

Re: [DISCUSS] MNG-7020 Remove Maven 2 WagonExcluder backward compat code

2021-02-06 Thread Tamás Cservenák
+1 fot option 3: we drag so much of legacy, that m4 really should accept maven 3.1+ plugins only (covers 14 years?). T On Sat, Feb 6, 2021, 14:32 Robert Scholte wrote: > (I'm not sure if this has already been discussed on the dev-list, but I > can't find any related thread) > > Plugins that dep

[DISCUSS] MNG-7020 Remove Maven 2 WagonExcluder backward compat code

2021-02-06 Thread Robert Scholte
(I'm not sure if this has already been discussed on the dev-list, but I can't find any related thread) Plugins that depend on maven-core 2.x will pull in Wagon, which causes unwanted behavior (it will superseed the one bundled with Maven for that plugin). MNG-7020 asks for removing this class,