This is an automated email from the ASF dual-hosted git repository.
gnodet pushed a change to branch backport-12083-to-4.0.x
in repository https://gitbox.apache.org/repos/asf/maven.git
discard 4dae3072d8 Trigger CI re-run
discard 8231330eda Fix domtrip API migration: child() → childElement(),
children() → childElements()
discard c75b417978 Fix Spotless formatting in CompatibilityFixStrategy
discard 2c8539a063 Fix #12080: mvnup - comment out dependencies with undefined
property expressions
add c2073d48e8 Fix domtrip API breakage after 1.5.1 upgrade (#12138)
add 947387de75 Fix #12080: mvnup - comment out dependencies with undefined
property expressions
add 56f5839a58 Fix Spotless formatting in CompatibilityFixStrategy
add 84bf5868e6 Fix domtrip API migration: child() → childElement(),
children() → childElements()
add ba9117e50d Trigger CI re-run
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 (4dae3072d8)
\
N -- N -- N refs/heads/backport-12083-to-4.0.x (ba9117e50d)
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:
