Am 2022-04-14 um 15:35 schrieb Christoph Läubrich:
Is there any plan when to release maven 3.8.6?
It depends whether or when all necessary tickets have been addressed. If
so, I'd go with a release something around 2022-05-08.
M
Is there any plan when to release maven 3.8.6?
Am 07.04.22 um 10:17 schrieb Tamás Cservenák:
... to not dissipate and reduce our (effort) losses :)
Howdy,
In short, I think we can agree on this sentence:
"we need to get rid of maven 3.8.x as fast as possible, release maven 3.9.x
and once out, k
Maybe something like on Node's page
https://nodejs.org/en/about/releases/
S.
śr., 13 kwi 2022, 22:21 użytkownik Hervé BOUTEMY
napisał:
> I near fully agree: I'd just replace "not maintained" with something like
> "stable"
>
> Le lundi 11 avril 2022, 18:44:31 CEST Manfred Moser a écrit :
> > I
I near fully agree: I'd just replace "not maintained" with something like
"stable"
Le lundi 11 avril 2022, 18:44:31 CEST Manfred Moser a écrit :
> I could not agree more. It is extremely important for users to understand
> that we are NOT a commercial entity providing support. And contrary to
> o
I could not agree more. It is extremely important for users to understand that
we
are NOT a commercial entity providing support. And contrary to other open source
products there is large, well known commercial entity either.
I also second all the other points from Tamas.
Manfred
Tamás Cservená
his definition, if
> > Maven 3.9.x requires Java 8 and a lot of plugins are also moving to
> > Java 8, then it effectively means that "older" versions will not be
> > supported by plugins (in the combination of Java 6 and 7).
> >
> > Welcome to the pandora box!
Errata below:
So, if for some business reason you are forced to use any pre Java 8 for
> development, you have two options:
> - use the latest Maven and toolchains targeting old Java
> - use the same versions of tools that are from the era when that Java was
> latest. Accept that with non-evolved
Welcome to the pandora box!
>
> On Mon, Apr 11, 2022 at 11:08 AM wrote:
> >
> > you're focusing on Maven core only
> > I'm talking about Maven = core + plugins
> >
> > and on Maven core, 3.9 and master are for new features, 3.8 is a
> stabilisation branch only
are
> considered stable
>
> does stable mean EOL?
>
> no, because it would mean that we only support unstable versions of Maven core
>
> - Mail original -
> De: "Slawomir Jaranowski"
> À: "Maven Developers List"
> Envoyé: Dimanche 10 A
ecause they are
considered stable
does stable mean EOL?
no, because it would mean that we only support unstable versions of Maven core
- Mail original -
De: "Slawomir Jaranowski"
À: "Maven Developers List"
Envoyé: Dimanche 10 Avril 2022 21:20:33
Objet: Re: We need to la
Am 2022-04-10 um 19:59 schrieb Hervé BOUTEMY:
Le dimanche 10 avril 2022, 09:56:46 CEST Michael Osipov a écrit :
Am 2022-04-10 um 09:10 schrieb Hervé BOUTEMY:
I think that the truth is that versions less than 3.8.x are also EOL.
no
please read the EOL message we took a lot of discussion to de
So..If I wanna make some refinements, I shall put them onto 4.0, means
master, right?
Slawomir Jaranowski 于2022年4月11日周一 03:20写道：
> our CI has running build for branches:
> - master
> - 3.9.x
> - 3.8.x
>
> It is only versions for which we can do changes, for others we simply don't
> have runni
our CI has running build for branches:
- master
- 3.9.x
- 3.8.x
It is only versions for which we can do changes, for others we simply don't
have running infrastructure, so the rest of the versions should be
officially mentioned as EOL.
To be clear we also should add information what kind of ch
Le dimanche 10 avril 2022, 09:56:46 CEST Michael Osipov a écrit :
> Am 2022-04-10 um 09:10 schrieb Hervé BOUTEMY:
>
> >> I think that the truth is that versions less than 3.8.x are also EOL.
> >
> > no
> > please read the EOL message we took a lot of discussion to define for
> > Maven
3.0.x:
> >
Am 2022-04-10 um 09:10 schrieb Hervé BOUTEMY:
I think that the truth is that versions less than 3.8.x are also EOL.
no
please read the EOL message we took a lot of discussion to define for Maven
3.0.x:
"Maven 3.0 has now reached its end of life. New plugin releases will require
Maven 3.1 or late
> I think that the truth is that versions less than 3.8.x are also EOL.
no
please read the EOL message we took a lot of discussion to define for Maven
3.0.x:
"Maven 3.0 has now reached its end of life. New plugin releases will require
Maven 3.1 or later."
yes, the definition of what "EOL" and "s
Hi,
Greate plan.
According to that we want don't support old version we should update
release history page [1]
We should clear communicate to user what is supported.
Now version less than 3.0.x are officially marked for EOL
I think that the truth is that versions less than 3.8.x are also EOL.
Howdy,
Just a short status update.
So, Maven bugfix 3.8.6 has all selected issues fixed, add more if you want
(remember, only regressions and super-trivial a'la logback):
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%203.8.6
Maven 3.9.0 has 2 new tasks a
I love that plan against 3.8.x, 3.9.x and 4
I did not really track details from 3.8.x, then I let others define what needs
to get in 3.8.6 to stabilize and let us focus on 3.9
Regards,
Hervé
Le jeudi 7 avril 2022, 10:17:56 CEST Tamás Cservenák a écrit :
> ... to not dissipate and reduce our (e
... to not dissipate and reduce our (effort) losses :)
Howdy,
In short, I think we can agree on this sentence:
"we need to get rid of maven 3.8.x as fast as possible, release maven 3.9.x
and once out, keep it on regression fixes until maven 4 is ready".
# Get rid of Maven 3.8.x
Hence, I think w
20 matches
Mail list logo
