Hi, +100 for 3.5.4 as minimum.
We should even consider 3.8.x. It is the fact that we only support the latest release version. We know how much work is in Maven core and how many plugins / components we support. And we know how many active maintainers we have. It should be clearly announced in documentation / on a page like "EOL / release policy / upgrade policy" - we don't have such or I can't find it. ( I wrote about it ...) By the way we also need a policy about deprecating features. Many times we try to have compatibility for very old features and many times code of components is complicated due to it. We should teach customers to use the latest version so upgrades should not be difficult for them. If somebody makes a decision to use the old version so it is their right and decision, and know the consequences. niedz., 13 mar 2022 o 18:29 Hervé BOUTEMY <[email protected]> napisał(a): > +1 to upgrade to Maven 3.5.4 prerequisite for future plugins releases > > what I'd like is that we better document compatibility updates: > - on Java prerequisites for components > - on Java and Maven prerequisites for plugins > > I found one community plugin that does a really excellent job at that [1] > I don't know if we should just add such a page in every component and > plugin, and make it a standard convention that is fullfilled by hand (and > will be fixed if we forgot some details) > or if we can automate some work > > probably we can start by hand: it's long overdue: it's what users need > when we update prerequisites, as we did in the past and we'll continue > because that's normal life > > Regards > > Hervé > > [1] > https://github.com/git-commit-id/git-commit-id-maven-plugin#plugin-compatibility-with-java > > Le dimanche 13 mars 2022, 12:48:03 CET Michael Osipov a écrit : > > Folks, > > > > as you might now we are dragging old luggage over and over with every > > new year. We are making (little) progress with cleansing, skimming and > > updating of our components. > > > > I'll will make a radical proposal I have already discussed privately > > with other fellow committers over Slack: > > Raise the entire baseline to Maven 3.5.4, all of our raises have been > > intermediaries. Reasoning: > > * Maven 3.5.4 is almost 4 old, it is settled > > * Everything before we shouls consider ancient, if you haven't moved > > yet, you will not and it will be your problem. > > * It is the first version which uses Maven Resolver [1] > > * It will free resources to test with previous releases which most don't > > do anyway > > * Maybe this will make it even easier to migrate to the upcoming Maven > > Core API > > > > WDYT? > > > > Michael > > > > PS: I don't even mind 3.6.3 personally, thought I don't this benefit. > > > > [1] > > > https://cwiki.apache.org/confluence/display/MAVEN/Maven+Ecosystem+Cleanup#Ma > > venEcosystemCleanup-ResolverandMaven > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Sławomir Jaranowski
