Thanks Anders, I found the page you mentioned at https://maven.apache.org/developers/compatibility-plan.html
I've read that and also the technical details wiki page at https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=155749857 The issue in question updates to Maven 3.1.0 dependencies so it can switch to Eclipse Aether, which is one of the explicitly mentioned reasons in the docs. I'll go ahead and process that issue. Dennis Lundberg Den fre 17 juli 2020 kl 09:13 skrev Anders Hammar <[email protected]>: > There's been some discussion regarding this lately and my take is that > we've settled on that requiring Maven 3.1.0 is ok for plugins. In the same > discussion I *think* we settled on that a Java 8 requirement is ok. > What I don't think we all agreed on is if it's ok to bump the requirements > without a real code need, or if there needs to be a need before we bump. So > it's up to each dev to decide when working on a plugin. > > There should even be a (draft) page outlining this. Don't have the URL at > hands right now though but it's in the list archive. > > /Anders > > On Fri, Jul 17, 2020 at 9:02 AM Dennis Lundberg <[email protected]> > wrote: > > > Hi, > > > > Where do we currently stand when it comes to the minimum version of > > Maven required by our plugins? Can a version 3.x Apache Maven plugin > > require something newer than Maven 3.0? > > > > The reason I ask is this > > https://issues.apache.org/jira/browse/MSHARED-936 > > which has the consequence that all plugins using maven-filtering will > need > > to bump their Maven prerequisite, if I understand correctly. > > > > -- > > Dennis Lundberg > > >
