er release.
thanks,
Robert
-- Origineel bericht --
Van: "Gary Gregory"
Aan: "Maven Developers List"
CC: "Rob Tompkins"
Verzonden: 24-10-2021 12:03:59
Onderwerp: Re: Upcoming Maven 3.8.4
That's the normal release process for any project AFAIK,
That's the normal release process for any project AFAIK, if you want to put
a release candidate out to on https://dist.apache.org/repos/dist/dev/ that
is done via svn, we've automated those steps.
Then the actual release goes to https://dist.apache.org/repos/dist/release/,
same for Maven https://d
Am 2021-10-23 um 21:48 schrieb Falko Modler:
Hi,
Given that we had two releases with regressions I tend *not* to merge
#578. Give it more time and thought.
As written before on GH, not merging #578 or a backport of #476 will
bring back MNG-6843.
This will catch users off guard that were happi
Hi,
Very strange release process for common components ... some of the
artifacts are published to the Central Repository and some of them are
published by svn repository ...
I don't see benefit for customizing maven core for one of case of usage
but it is discussion for another place, here I only
HI All:
I discovered a regression this morning that prevents me from creating
a release candidate for Apache Commons CLI:
https://issues.apache.org/jira/browse/MNG-7316
https://github.com/apache/maven/pull/601
May this be included for 3.8.4 please?
Gary
On Sat, Oct 23, 2021 at 3:48 PM Falko Mo
Hi,
Given that we had two releases with regressions I tend *not* to merge
#578. Give it more time and thought.
As written before on GH, not merging #578 or a backport of #476 will
bring back MNG-6843.
This will catch users off guard that were happily benefitting from
MNG-6843 being fixed in 3.
Folks,
all important tickets for Maven 3.8.4 have been addressed in maven-3.8.x
branch.
We have two open PRs:
* #578: Alternative to the ThreadLocal approach
* #476: As far as I understand a more global approach to the issue and
supersedes #576, but requires Java 8. So Maven 3.9+
Given that
