This is an automated email from the ASF dual-hosted git repository.
gnodet pushed a change to branch gh-11772-consumer-pom-validation
in repository https://gitbox.apache.org/repos/asf/maven.git
discard de91c68d1c [GH-11772] Fix remaining CI failures: scope validation to
POM packaging only
discard e445b49cc9 [GH-11772] Fix CI failures: revert build POM resolution and
fix consumer POM validation
discard edf1c471e9 [GH-11772] Remove stripTo400 — rely on model version check
and fail-fast
discard 206370bf0c [GH-11772] Add IT verifying consumer POMs are 4.0.0 for
4.1.0 projects
discard 570ac26246 [GH-11772] Add unit tests for consumer POM 4.1.0 feature
stripping
discard 2d16801cf9 [GH-11772] Strip 4.1.0 features from parent consumer POMs
to produce 4.0.0
discard 6f47d8d46c [GH-11772] Resolve build POM for parent resolution during
builds
discard d39081265b [GH-11772] Add managed dep removal flag and consumer POM
validation
add 8b30eac121 [GH-11772] Fail-fast consumer POM validation for non-4.0.0
model versions
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 (de91c68d1c)
\
N -- N -- N refs/heads/gh-11772-consumer-pom-validation
(8b30eac121)
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:
