wt., 9 sty 2024 o 10:45 Tamás Cservenák <ta...@cservenak.net> napisał(a):

> Howdy,
>
> I still think we need to modify few bits here and there:
> - we MUST compile against latest maven (3.9.6 currently)
>

Step by step - it can be a next task


> - this thread (as I see) is about "minimal prerequisite" for plugin (so
> POM/prerequisite)
> - to address issues Slawek brought up, we need at least to modify this
> stanza in CI:
>
> https://github.com/apache/maven-gh-actions-shared/blob/v3/.github/workflows/maven-verify.yml#L50
> and build with "minimal prerequisite" and "current" at least, so matrix of
> Maven would be generally array [ "3.6.3", "3.9.6" ] as this would catch any
> problem Slawek brought up
>

Done in: https://github.com/apache/maven-gh-actions-shared/pull/93


>
> As if we keep building against versions released 2-5-10 years ago, whatever
> we deprecate in 3.9.x is never picked up.
>
> Thanks
> T
>
>
> On Tue, Jan 9, 2024 at 9:13 AM Slawomir Jaranowski <s.jaranow...@gmail.com
> >
> wrote:
>
> > pt., 5 sty 2024 o 20:49 Slawomir Jaranowski <s.jaranow...@gmail.com>
> > napisał(a):
> >
> > >
> > >
> > > pt., 5 sty 2024 o 16:17 Michael Osipov <micha...@apache.org>
> napisał(a):
> > >
> > >> On 2024/01/05 14:03:11 Slawomir Jaranowski wrote:
> > >> > Hi,
> > >> >
> > >> > My summary for this discussion:
> > >> >
> > >> > No objection for change: Tamás Cservenák, Anders Hammar, Olivier
> Lamy,
> > >> > Sylwester Lachiewicz, Jorge Solórzano, Gary Gregory, Hervé Boutemy
> > >> >
> > >> > Michael Osipov - had a questions but I assume that is no -1 from him
> > >>
> > >> Clearly not -1, I just want to see a plan before I give a reasonable
> > vote.
> > >>
> > >>
> > > Can you remember me what plan or procedure we have followed during
> > > switching plugins requirements to 3.2.5.
> > >
> > >
> >
> >  Michael kindly remember - what plan do you want to see?
> >
> > For me is:
> >  - update documentation - https://github.com/apache/maven-site/pull/484
> >  - announce to users
> >  - start using 3.6.3 in plugins, I don't think we need a special releases
> > cycles with such updates for all plugins, we release new version when is
> > needed, requested and so on
> >
> > I don't want to wait forever for it.
> >
> > > So:
> > >> >
> > >> > I would like to not categorize cora and not core plugins - simply we
> > >> have a
> > >> > list of plugins which is maintain by Maven team:
> > >> > https://maven.apache.org/plugins/index.html
> > >>
> > >> We have that already in the above mention page..
> > >>
> > >> > I will send a dedicated email to the dev and users list about plans.
> > >>
> > >> Can you prepare a draft first, please?
> > >>
> > >>
> > > Yes I can prepare one.. but old email in such cases like make version
> EOL
> > > or switching requirements for plugins will be helpful.
> > >
> > >
> > >
> > >> > I will update documentations and sites about new requirements:
> > >> >  - https://maven.apache.org/developers/compatibility-plan.html
> > >> >  - https://maven.apache.org/docs/history.html
> > >> >  -
> > >>
> >
> https://cwiki.apache.org/confluence/display/MAVEN/Maven+Ecosystem+Cleanup
> > >> >
> > >> > With nexts release of plugins we should add "Requirements History"
> > >> >
> > >> > We have a list of current Plugins requirements:
> > >> >
> > >>
> >
> https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-dist-tool/job/master/site/dist-tool-prerequisites.html
> > >>
> > >> Lookting at these, I'd like to see the retirement of all 2.2.1
> > compatible
> > >> plugins. No one found the time/motivation/need to left them to 3.x. We
> > >> should clear the premises before we raise the bar otherwise that does
> > not
> > >> look good at all.
> > >>
> > >> Thanks for working on this...
> > >>
> > >> M
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > >> For additional commands, e-mail: dev-h...@maven.apache.org
> > >>
> > >>
> > >
> > > --
> > > Sławomir Jaranowski
> > >
> >
> >
> > --
> > Sławomir Jaranowski
> >
>


-- 
Sławomir Jaranowski

Reply via email to