I think we've previously agreed to push the minimum version for plugins to 3.1.0.
I've tried this in multiple plugins though and it is non-trivial; definitely not as simple as setting mavenVersion to 3.1.0 or later. There seem to be some complicated interdependencies between maven core, org,sonatype.aether, org.eclipse, aether, maven-plugin-testing-harness, and parts of plexus that all have to be upgraded at the same time. Furthermore code changes in .java files are also required, not just changes in pom.xml. I don't have a full understanding of the issues, and as I said, I haven't successfully upgraded a plugin to Maven 3.1 yet. On Wed, Apr 15, 2020 at 4:39 PM Tibor Digana <[email protected]> wrote: > > Some users still use Maven 3.0.5 and they require a support for > compatibility reasons between nowadays Maven plugins and the Maven > 3.0.x. > > We have a couple of reasons to deprecate this version (JSR-330, > Components injection, Logger) and we have discussed this issue in > https://github.com/apache/maven-surefire/pull/274 > > Let's discuss it. > > Cheers > Tibor17 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > -- Elliotte Rusty Harold [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
