This is an automated email from the ASF dual-hosted git repository.

gnodet pushed a change to branch mvnup
in repository https://gitbox.apache.org/repos/asf/maven.git


 discard f8792df341 Remove duplicate headers
     add f828473e7d Remove duplicate headers
     add 4c7f2f6153 feat: add parent POM plugin detection with proper XML 
formatting

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   (f8792df341)
            \
             N -- N -- N   refs/heads/mvnup (4c7f2f6153)

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:
 .../invoker/mvnup/goals/ParentPomResolver.java     | 39 ++++++++++------------
 .../invoker/mvnup/goals/PluginUpgradeTest.java     | 21 +++++++++---
 2 files changed, 33 insertions(+), 27 deletions(-)

Reply via email to