The majority of our commonly used plugins use 3.2.5 as a prerequisite [1]. We could soon migrate a few more. To me, upgrading to last year's agreed 3.5.4 is worth it for "our" plugins only - so we can test it more or less internally before projects outside. Biggest change is mentioned by Michael - switch to the new, renamed Resolver artefact. With the update to 3.2.5 everyone made a huge effort to clean up tech debt.
But also, with the new pom release we can send "deprecation" messages (jira in release notes?) to other projects. Sylwester [1] https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-dist-tool/job/master/site/dist-tool-prerequisites.html sob., 1 kwi 2023 o 11:07 Slawomir Jaranowski <[email protected]> napisał(a): > sob., 1 kwi 2023 o 11:02 Sylwester Lachiewicz <[email protected]> > napisał(a): > > > 3.5.4 - this is for Maven plugins - not globally for ASF pom > > > > It is globally for ASF pom - https://maven.apache.org/pom/asf/ > > > > > > sob., 1 kwi 2023 o 11:01 Sylwester Lachiewicz <[email protected]> > > napisał(a): > > > > > +1 to bump it to 2.5.4 as we decided last year > > > > > > Sylwester > > > > > > sob., 1 kwi 2023 o 09:56 Slawomir Jaranowski <[email protected]> > > > napisał(a): > > > > > >> Hi > > >> > > >> We have set minimalMavenBuildVersion to 3.2.5 > > >> > > >> But we have a plan to move minimum Maven requirements for plugins to > > 3.5.4 > > >> or maybe even 3.6.3 > > >> > > >> For Maven projects on CI systems we use at least Maven 3.6.3 - I don't > > >> know > > >> about other ASF projects. > > >> > > >> So the question is - should we bump the minimalMavenBuildVersion to a > > >> higher version? > > >> > > >> -- > > >> Sławomir Jaranowski > > >> > > > > > > > > -- > Sławomir Jaranowski >
