This is an automated email from the ASF dual-hosted git repository.
gnodet pushed a change to branch backport/11901-to-maven-4.0.x
in repository https://gitbox.apache.org/repos/asf/maven.git
discard 1b392858f6 Fix logging setup/teardown order (#11901)
add c2073d48e8 Fix domtrip API breakage after 1.5.1 upgrade (#12138)
add faa69c9b9c Fix logging setup/teardown order (#11901)
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (1b392858f6)
\
N -- N -- N refs/heads/backport/11901-to-maven-4.0.x (faa69c9b9c)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
.../org/apache/maven/cling/invoker/mvnup/goals/AbstractUpgradeGoal.java | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
