This is an automated email from the ASF dual-hosted git repository.
gnodet pushed a change to branch plume-football
in repository https://gitbox.apache.org/repos/asf/maven.git
discard 06045e0cf2 [MNG-11642] Add JPMS module support to Maven 4
add f254df73af [MNG-11966] Update lifecycles reference to point to
LifecycleRegistry (#12260)
add e88a2e436a [ISSUE-10329] Document behaviour of UrlNormalizer (#12293)
add 2e352ec639 Add deprecation Javadoc to XmlNode constants and methods
(#11576)
add ea5829e600 [MNG-11642] Add JPMS module support to Maven 4
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 (06045e0cf2)
\
N -- N -- N refs/heads/plume-football (ea5829e600)
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:
.../maven/api/services/model/UrlNormalizer.java | 9 ++-
.../java/org/apache/maven/api/xml/XmlNode.java | 64 ++++++++++++++++++--
impl/maven-core/src/site/apt/lifecycles.apt.vm | 2 +-
impl/maven-impl/src/main/java/module-info.java | 6 ++
.../maven/impl/DefaultUrlNormalizerTest.java | 69 ++++++++++++++++++++++
impl/maven-jline/src/main/java/module-info.java | 3 +
6 files changed, 145 insertions(+), 8 deletions(-)
create mode 100644
impl/maven-impl/src/test/java/org/apache/maven/impl/DefaultUrlNormalizerTest.java
