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 <[email protected]> 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
> <[email protected]> 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
> > <[email protected]> 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 <[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+Cleanup#MavenEcosystemCleanup-ResolverandMaven
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: [email protected]
> > > > For additional commands, e-mail: [email protected]
> > > >
> > >
> > >
> > > --
> > > Elliotte Rusty Harold
> > > [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]
>
>

-- 
Sławomir Jaranowski

Reply via email to