Le lun. 14 mars 2022 à 08:43, Hervé BOUTEMY <[email protected]> a écrit :
> Le lundi 14 mars 2022, 08:01:11 CET Maarten Mulders a écrit : > > Just to clarify: "Raise the entire baseline to Maven 3.5.4" means that > > the official Maven plugins will only work from Maven Core 3.5.4 onwards? > yes > > > In that case, +1 to move the baseline to 3.5.4. > > > > > Point of concern/question: this may be a breaking change in some cases - > > how do we communicate that in terms of versioning? Ideally - I'd say - a > > 3.x plugin works on Maven 3.x, a future 4.x plugin works on Maven 4.x, > > etc... > that's why I was proposing to document properly, for example like > > https://github.com/git-commit-id/git-commit-id-maven-plugin#plugin-compatibility-with-java > > > > > Also, I agree with Eliotte when it comes to package managers. Even > > though we do not maintain those ourselves, it's a fact that many people > > use them to install software on their machines, including Maven. Acting > > as if it's none of our business would probably equal ignoring those > users. > if someone wants to start a page on Maven Site, so everybody can > contribute by > proposing a PR, that would be nice > > > >> Even more ambitiously, perhaps we should rethink how maven is > > >> installed. Why should it come from anywhere but Maven Central, and why > you know what, it's what Maven Wrapper is about :) > Just to answer to the "why": cause some distro (several actually) only accept to build from sources ;). To also avoid an ambiguity: maven wrapper is not a package manager so it does not solve the issue (sdkman/chocolatey are for ex). Question for me is: do we want to do as gradle and bind the build tool to the project or do we want to keep our nice compatibility which enables most of dev to have a smooth experience without caring of a lot of details. I'm indeed for our current philosophy but if it costs too much we should probably make our distro abuse of our IoC and central to download what is needed to be compatible maybe? > > Regards, > > Hervé > > > > > > > Maarten > > > > On 13/03/2022 22:04, Enrico Olivelli wrote: > > > +1 > > > > > > Thanks for bringing this up > > > > > > Enrico > > > > > > Il giorno dom 13 mar 2022 alle ore 20:58 Elliotte Rusty Harold > > > > > > <[email protected]> ha scritto: > > >> What do all the various package managers install? I'm pretty sure I've > > >> seen one lately whose default was 3.3.1. Debian perhaps? > > >> > > >> I think before we make any such move it would make sense to audit what > > >> people who don't manually install Maven are likely to have. First we > > >> should raise all those to 3.5.4 or later. Then we can upgrade the > > >> minimum version. > > >> > > >> Even more ambitiously, perhaps we should rethink how maven is > > >> installed. Why should it come from anywhere but Maven Central, and why > > >> can't a pom.xml specify the version of Maven itself? All we really > > >> should install is a very simple bootstrap script. But that's probably > > >> a discussion for another day. Let's get the package managers > > >> straightened out first. > > >> > > >> On Sun, Mar 13, 2022 at 11:48 AM Michael Osipov <[email protected]> > > wrote: > > >>> 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+Cleanu > > >>> p#MavenEcosystemCleanup-ResolverandMaven > > >>> > > >>> --------------------------------------------------------------------- > > >>> To unsubscribe, e-mail: [email protected] > > >>> For additional commands, e-mail: [email protected] > > >> > > >> -- > > >> Elliotte Rusty Harold > > >> [email protected] > > >> > > >> --------------------------------------------------------------------- > > >> 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] > > > > --------------------------------------------------------------------- > > 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] > >
