Even though we release the Maven APIs together with Maven Core (with the same version), for plugins there are close to no changes. The biggest changes of Maven APIs are from 2.2.1 to 3.0 and 3.0.5 to 3.1.0 With this in mind, having almost all plugins depending on 3.0, it makes sense to start moving to 3.1.0 I don't see any benefit to require a higher version of Maven. And it doesn't come with extra maintenance costs. So there must be a better reason, e.g. if a plugin requires a specific implementation of Maven, (like the upcoming maven-wrapper-plugin). I'd created a page to migrate plugins to Maven 3.0 and I thought I prepared on for 3.1.0 as well, but can't find it. One benefit of requiring Maven 3.1.0 is replacing the plexus annotations with JSR330 since this is the current standard, much better to understand for the average developer. (not the Maven Plugin Annotations!)
Robert [1] https://cwiki.apache.org/confluence/display/MAVEN/Plugin+migration+to+Maven3+dependencies On 6-3-2020 14:19:09, Mickael Istria <mist...@redhat.com> wrote: Hi, Community support is always an interesting question as there is no support contract to define what "support" means ;) IMO, the community does at least support the latest release. Then if some community members can work on supporting older ones, that's good, but IMO it doesn't have to be the priority of the community to support older versions if it slows down main development. Long term support is something expensive to provide, and that some companies can bill for; unless the companies that bill for older version support do invest back with contributors in the project to provide such support in the community channels, then it's just so much simpler and more fair to say that community only supports latest release and drop all older ones, and let people who can make money with it take care of older support from people who are ready to pay for it. Cheers
