Am 2017-05-15 um 09:20 schrieb Stephen Connolly:
On Sun 14 May 2017 at 08:51, Hervé BOUTEMY <herve.bout...@free.fr> wrote:
thank you Robert: this is exactly the logic I was looking for, and
explanation
of changes over time to improve user experience through reproducibility.
Now the question is: should we change default plugin versions in Maven
core?
Does it improve Maven or not?
I think we should.
If we don't update, we have a more complex ux for new users.
We already say to pin versions (iirc we even log warnings)
If people choose to ignore the warnings of a build being at risk of
differential behaviour... they get what they configured: differential builds
To me, changing default plugin versions lowers reproducibility.
Which is why we warn users... and the warning is there *to allow us to
upgrade*
And it does not help users learn that they should define their own plugin
versions instead of depending on the magic defaults that have to be
included
in Maven core to permit basic poms.
We do not have two opposite opinions on this. What now, what to do with
the branch?
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
