You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Michael Osipov <mi...@apache.org> on 2022/03/13 11:48:03 UTC
[DISCUSS] Radical Fast Forward to 3.5.4
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#MavenEcosystemCleanup-ResolverandMaven
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSS] Radical Fast Forward to 3.5.4
Posted by Michael Osipov <mi...@apache.org>.
Technically, you are right. We request to verify issues with 3.8.x and
move to if the issue is resolved. But that does not happen very often,
IMHO. I wouldn't even object to raise to 3.8.1, but this is another
discussion.
Am 2022-03-13 um 16:45 schrieb Sylwester Lachiewicz:
> Everything before 3.8.x now it's obsolete, because we no longer provide or
> plan any patches to the 3.5x or 3.6x line (bugfix or security)
>
> Sylwester
>
> niedz., 13 mar 2022, 12:48 użytkownik Michael Osipov <mi...@apache.org>
> napisał:
>
>> 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#MavenEcosystemCleanup-ResolverandMaven
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
Re: [DISCUSS] Radical Fast Forward to 3.5.4
Posted by Sylwester Lachiewicz <sl...@gmail.com>.
Everything before 3.8.x now it's obsolete, because we no longer provide or
plan any patches to the 3.5x or 3.6x line (bugfix or security)
Sylwester
niedz., 13 mar 2022, 12:48 użytkownik Michael Osipov <mi...@apache.org>
napisał:
> 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#MavenEcosystemCleanup-ResolverandMaven
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: [DISCUSS] Radical Fast Forward to 3.5.4
Posted by Guillaume Nodet <gn...@apache.org>.
+1 to upgrade plugins / components
Le dim. 13 mars 2022 à 12:48, Michael Osipov <mi...@apache.org> 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#MavenEcosystemCleanup-ResolverandMaven
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
------------------------
Guillaume Nodet
Re: [DISCUSS] Radical Fast Forward to 3.5.4
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Le lun. 14 mars 2022 à 08:43, Hervé BOUTEMY <he...@free.fr> 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
> > >
> > > <el...@ibiblio.org> 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 <mi...@apache.org>
>
> 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: dev-unsubscribe@maven.apache.org
> > >>> For additional commands, e-mail: dev-help@maven.apache.org
> > >>
> > >> --
> > >> Elliotte Rusty Harold
> > >> elharo@ibiblio.org
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > >> For additional commands, e-mail: dev-help@maven.apache.org
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: dev-help@maven.apache.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: [DISCUSS] Radical Fast Forward to 3.5.4
Posted by Hervé BOUTEMY <he...@free.fr>.
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 :)
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
> >
> > <el...@ibiblio.org> 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 <mi...@apache.org>
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: dev-unsubscribe@maven.apache.org
> >>> For additional commands, e-mail: dev-help@maven.apache.org
> >>
> >> --
> >> Elliotte Rusty Harold
> >> elharo@ibiblio.org
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: dev-help@maven.apache.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSS] Radical Fast Forward to 3.5.4
Posted by Maarten Mulders <mt...@apache.org>.
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?
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...
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.
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
> <el...@ibiblio.org> 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 <mi...@apache.org> 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+Cleanup#MavenEcosystemCleanup-ResolverandMaven
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>
>>
>> --
>> Elliotte Rusty Harold
>> elharo@ibiblio.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSS] Radical Fast Forward to 3.5.4
Posted by Enrico Olivelli <eo...@gmail.com>.
+1
Thanks for bringing this up
Enrico
Il giorno dom 13 mar 2022 alle ore 20:58 Elliotte Rusty Harold
<el...@ibiblio.org> 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 <mi...@apache.org> 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+Cleanup#MavenEcosystemCleanup-ResolverandMaven
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
>
>
> --
> Elliotte Rusty Harold
> elharo@ibiblio.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSS] Radical Fast Forward to 3.5.4
Posted by Bernd Eckenfels <ec...@zusammenkunft.net>.
Hello,
I really think no sane developer should use stable distributions like EL or Debian für Java/Maven toolchains. But if they do, they do know they have old software and their vendor will do the maintenance. I would not be concerned with that (besides maybe clearly communicating EOLs, minimum versions and requirements). Of course you could try to negotiate with the biggest distributions on a common ground, but that will mean more versions than today (not less) - so why waste your cycles…
Gruss
Bernd
--
http://bernd.eckenfels.net
________________________________
Von: Jorge Solórzano <jo...@gmail.com>
Gesendet: Monday, March 14, 2022 4:31:35 PM
An: Maven Developers List <de...@maven.apache.org>
Betreff: Re: [DISCUSS] Radical Fast Forward to 3.5.4
FYI, it looks like RHEL-based 7 uses maven 3.0.5, RHEL-based 8 uses
3.5.4 and 3.6.3.
My guess is that even if the new upgraded plugins depend on Maven
3.5.4 it wouldn't cause major issues as if anyone is using an olver
Maven version they will likely use older versions of the
plugins/components.
Anyway, as Hervé mentioned, there is a lack of better documentation of
the compatibility of plugins, and based on this page
https://maven.apache.org/developers/compatibility-plan.html since Jun
2020, plugins can have Java 8 prerequisite, and even for Maven 3.8.x
that means a breaking change.
On Mon, Mar 14, 2022 at 3:40 PM Elliotte Rusty Harold
<el...@ibiblio.org> wrote:
>
> FYI Debian Stable is at 3.6.3 as is Ubuntu. Homebrew is at 3.8. I've
> only checked the websites for this, not tried to install from there.
> However neither looks like a blocker.
>
> What other package managers should we check? What does Red Hat use? Windows?
>
> Also, are there any older versions of OS's likely to be in use that
> have older package managers?
>
>
>
> On Sun, Mar 13, 2022 at 7:57 PM Elliotte Rusty Harold
> <el...@ibiblio.org> wrote:
> >
> > 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 <mi...@apache.org> 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+Cleanup#MavenEcosystemCleanup-ResolverandMaven
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: dev-help@maven.apache.org
> > >
> >
> >
> > --
> > Elliotte Rusty Harold
> > elharo@ibiblio.org
>
>
>
> --
> Elliotte Rusty Harold
> elharo@ibiblio.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSS] Radical Fast Forward to 3.5.4
Posted by Slawomir Jaranowski <s....@gmail.com>.
Hi,
As I and others wrote - we should have clear documentation about release
and version policy.
Maintainers / contributors of package managers should take care about
updating their products. It can not be our responsibility and moreover a
blocker for us.
We have basic instructions on how to install Maven, it doesn't even require
administrator privilege - Maven can be installed in user space.
pon., 14 mar 2022 o 16:32 Jorge Solórzano <jo...@gmail.com> napisał(a):
> FYI, it looks like RHEL-based 7 uses maven 3.0.5, RHEL-based 8 uses
> 3.5.4 and 3.6.3.
>
> My guess is that even if the new upgraded plugins depend on Maven
> 3.5.4 it wouldn't cause major issues as if anyone is using an olver
> Maven version they will likely use older versions of the
> plugins/components.
>
> Anyway, as Hervé mentioned, there is a lack of better documentation of
> the compatibility of plugins, and based on this page
> https://maven.apache.org/developers/compatibility-plan.html since Jun
> 2020, plugins can have Java 8 prerequisite, and even for Maven 3.8.x
> that means a breaking change.
>
>
> On Mon, Mar 14, 2022 at 3:40 PM Elliotte Rusty Harold
> <el...@ibiblio.org> wrote:
> >
> > FYI Debian Stable is at 3.6.3 as is Ubuntu. Homebrew is at 3.8. I've
> > only checked the websites for this, not tried to install from there.
> > However neither looks like a blocker.
> >
> > What other package managers should we check? What does Red Hat use?
> Windows?
> >
> > Also, are there any older versions of OS's likely to be in use that
> > have older package managers?
> >
> >
> >
> > On Sun, Mar 13, 2022 at 7:57 PM Elliotte Rusty Harold
> > <el...@ibiblio.org> wrote:
> > >
> > > 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 <mi...@apache.org>
> 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+Cleanup#MavenEcosystemCleanup-ResolverandMaven
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: dev-help@maven.apache.org
> > > >
> > >
> > >
> > > --
> > > Elliotte Rusty Harold
> > > elharo@ibiblio.org
> >
> >
> >
> > --
> > Elliotte Rusty Harold
> > elharo@ibiblio.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
Sławomir Jaranowski
Re: [DISCUSS] Radical Fast Forward to 3.5.4
Posted by Jorge Solórzano <jo...@gmail.com>.
FYI, it looks like RHEL-based 7 uses maven 3.0.5, RHEL-based 8 uses
3.5.4 and 3.6.3.
My guess is that even if the new upgraded plugins depend on Maven
3.5.4 it wouldn't cause major issues as if anyone is using an olver
Maven version they will likely use older versions of the
plugins/components.
Anyway, as Hervé mentioned, there is a lack of better documentation of
the compatibility of plugins, and based on this page
https://maven.apache.org/developers/compatibility-plan.html since Jun
2020, plugins can have Java 8 prerequisite, and even for Maven 3.8.x
that means a breaking change.
On Mon, Mar 14, 2022 at 3:40 PM Elliotte Rusty Harold
<el...@ibiblio.org> wrote:
>
> FYI Debian Stable is at 3.6.3 as is Ubuntu. Homebrew is at 3.8. I've
> only checked the websites for this, not tried to install from there.
> However neither looks like a blocker.
>
> What other package managers should we check? What does Red Hat use? Windows?
>
> Also, are there any older versions of OS's likely to be in use that
> have older package managers?
>
>
>
> On Sun, Mar 13, 2022 at 7:57 PM Elliotte Rusty Harold
> <el...@ibiblio.org> wrote:
> >
> > 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 <mi...@apache.org> 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+Cleanup#MavenEcosystemCleanup-ResolverandMaven
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: dev-help@maven.apache.org
> > >
> >
> >
> > --
> > Elliotte Rusty Harold
> > elharo@ibiblio.org
>
>
>
> --
> Elliotte Rusty Harold
> elharo@ibiblio.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSS] Radical Fast Forward to 3.5.4
Posted by Elliotte Rusty Harold <el...@ibiblio.org>.
FYI Debian Stable is at 3.6.3 as is Ubuntu. Homebrew is at 3.8. I've
only checked the websites for this, not tried to install from there.
However neither looks like a blocker.
What other package managers should we check? What does Red Hat use? Windows?
Also, are there any older versions of OS's likely to be in use that
have older package managers?
On Sun, Mar 13, 2022 at 7:57 PM Elliotte Rusty Harold
<el...@ibiblio.org> wrote:
>
> 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 <mi...@apache.org> 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+Cleanup#MavenEcosystemCleanup-ResolverandMaven
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
>
>
> --
> Elliotte Rusty Harold
> elharo@ibiblio.org
--
Elliotte Rusty Harold
elharo@ibiblio.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSS] Radical Fast Forward to 3.5.4
Posted by Elliotte Rusty Harold <el...@ibiblio.org>.
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 <mi...@apache.org> 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+Cleanup#MavenEcosystemCleanup-ResolverandMaven
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
--
Elliotte Rusty Harold
elharo@ibiblio.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSS] Radical Fast Forward to 3.5.4
Posted by Michael Osipov <mi...@apache.org>.
I don't think this is so easy. While working on Doxia we have noticed
that a lot of intertwined and as soon as you touch on component you need
to touch the rest also.
At least a one time pain we must go.
Am 2022-03-13 um 12:52 schrieb Romain Manni-Bucau:
> Hi,
>
> No big issue with me but I would also consider letting v3 as it is and
> start working on v4 with an alpha coming soon maybe?
> Can be a way to reach these goals without impacting twice end users too.
>
> Le dim. 13 mars 2022 à 12:48, Michael Osipov <mi...@apache.org> 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#MavenEcosystemCleanup-ResolverandMaven
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
Re: [DISCUSS] Radical Fast Forward to 3.5.4
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Hi,
No big issue with me but I would also consider letting v3 as it is and
start working on v4 with an alpha coming soon maybe?
Can be a way to reach these goals without impacting twice end users too.
Le dim. 13 mars 2022 à 12:48, Michael Osipov <mi...@apache.org> 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#MavenEcosystemCleanup-ResolverandMaven
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: [DISCUSS] Radical Fast Forward to 3.5.4
Posted by Tamás Cservenák <ta...@cservenak.net>.
+1
On Sun, Mar 13, 2022, 12:48 Michael Osipov <mi...@apache.org> 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+Cleanup#MavenEcosystemCleanup-ResolverandMaven
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: [DISCUSS] Radical Fast Forward to 3.5.4
Posted by Slawomir Jaranowski <s....@gmail.com>.
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 <he...@free.fr>
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: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
Sławomir Jaranowski
Re: [DISCUSS] Radical Fast Forward to 3.5.4
Posted by Hervé BOUTEMY <he...@free.fr>.
+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: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[SUMMARY] [DISCUSS] Radical Fast Forward to 3.5.4
Posted by Michael Osipov <mi...@apache.org>.
I'd like to distill what has been discussed and favored so far by
respondees and how we should proceed in the future:
* Cut off old ties and favorize move to 3.5.4 as a new baseline
* Have downstream users follow us and us follow them
* Establish proper documentation on our baseline rules
* Some have even expressed the opinion to raise the base to 3.8.x
I think going from 3.5.4 to 3.8.x is much easier than from 3.0.x or 3.1.x.
Next steps:
* Create cwiki page [1] which documents the status of each component and
plugin requiring a specific Maven version and a JIRA issue which
documents ugrade to Maven 3.5.4
* Discuss how to properly document those changes
Michael
[1]
https://cwiki.apache.org/confluence/display/MAVEN/Baseline+Upgrade+to+Maven+3.5.4
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org