Hi, Yes, there are multiple reasons: 1. you should not rely on default version (defined in Maven version your using) but lock your own choice in your pom (or parent) 2. for people not having locked their version, having a change of default version based on Maven version is a side effect we want to avoid
Then letting the same (old) version by default as the default that was defined in Maven 3.0 is the best we can do until now to help users apply good practice. In Maven 3.7, if you did not lock your plugin version but use default version, you'll get a warning: see MNG-6562 [1] That will be a better incentive to lock down your versions than keeping the same version as Maven 3.0 Then in Maven 3.7, with the warning in place, we may upgrade default versions (I still don't like it, but the warning logged by MNG-6562 will at least be there) Regards, Hervé [1] https://issues.apache.org/jira/browse/MNG-6562 Le mercredi 12 juin 2019, 11:09:53 CEST François Guillot a écrit : > Hi, > > The default Surefire version in Maven is 2.12.4, which is very old. > Any reason to not upgrade it to a more recent version ? > > Thanks > > François --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
