Seems to me that fixes are never back-ported, meaning only the latest version of Maven is really supported. That being said, care also seems to be taken to not make changes in plugins which break older versions of Maven. I think you ask an important question, because trying to keep plugins working on older versions of Maven possibly means not being able to solve things in a way one would like to. Older versions limit choices. So that is a cost. I don't know how many users there who insist on keeping an older version of Maven itself but want the latest plugins..I wouldn't mind personally if the Maven project more aggressively lifted the floor if that means better implementations due to more freedom.
- Eric L On Fri, Mar 6, 2020 at 2:04 PM Elliotte Rusty Harold <elh...@ibiblio.org> wrote: > We're coming up on the ten year anniversary of Maven 3.0. > > Maven 3.2.5 was, I think, the first to support Java 6. > > 3.3.9 is five years old. > > Some of our documentation still references Maven 2 and Maven 3 as if > the difference matters. It does, but we can mostly just assume Maven > 3, I think, and ignore Maven 2. > > Is it time to stop worrying about Maven 3.0 for plugin support? If so, > what's the minimum version we should support? 3.1.0? 3.3.9? 3.5.0? > > > -- > Elliotte Rusty Harold > elh...@ibiblio.org > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
