Le jeu. 14 juil. 2022 à 09:34, Slawomir Jaranowski
a écrit :
> czw., 14 lip 2022 o 08:02 Romain Manni-Bucau
> napisał(a):
>
> > A few points on that topic:
> >
> > 1. Helping users is always +1000
> > 2. Some plugins do check if there is a new version and log it => a. makes
> > the build not
czw., 14 lip 2022 o 08:02 Romain Manni-Bucau
napisał(a):
> A few points on that topic:
>
> 1. Helping users is always +1000
> 2. Some plugins do check if there is a new version and log it => a. makes
> the build not highly reproduceable (logs) b. pollutes user info most of the
> time
> 3.
A few points on that topic:
1. Helping users is always +1000
2. Some plugins do check if there is a new version and log it => a. makes
the build not highly reproduceable (logs) b. pollutes user info most of the
time
3. Versions are not always an user choice (software architect and whatever
rules
So simply put Maven is stopping support of plugins that have not been
updated for about 9 years (Maven 3.1.0 is in 2 days 9 years old).
I say go for it.
Niels
On Wed, 13 Jul 2022, 15:54 Tamás Cservenák, wrote:
> Howdy,
>
> for starter, read comments on this PR:
>
+1 from me.
We should inform users about good practices like using the newest plugin
versions.
Yes it can be true that authors of plugins do not maintain it in the proper
way but with pressure from Maven and informed users it can happen early.
Now not many people take care about such things,
Howdy,
for starter, read comments on this PR:
https://github.com/apache/maven/pull/765
TL;DR
Intent of "experiment" was to warn those users who use Maven2 plugins ("old
plugins") with Maven3.9+.
Reasoning: Maven 3.9 is "taking turn" toward Maven4, and just like Maven3
did support Maven2 plugins,
