You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by sj...@apache.org on 2023/10/26 20:10:10 UTC

[maven-apache-parent] branch MPOM-431 updated (25dc913 -> 19c4ad7)

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

sjaranowski pushed a change to branch MPOM-431
in repository https://gitbox.apache.org/repos/asf/maven-apache-parent.git


    omit 25dc913  [MPOM-431] Bump maven-clean-plugin from 3.2.0 to 3.3.1
     add 1ebc46c  [MPOM-435] Bump maven-war-plugin from 3.3.2 to 3.4.0
     add 1d9989c  [MPOM-432] Bump maven-enforcer-plugin from 3.3.0 to 3.4.1
     add 92f1deb  [MPOM-433] Bump maven-invoker-plugin from 3.5.1 to 3.6.0
     add 34f55e9  [MPOM-434] Bump maven-shade-plugin from 3.4.1 to 3.5.1
     add 19c4ad7  [MPOM-431] Bump maven-clean-plugin from 3.2.0 to 3.3.2

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   (25dc913)
            \
             N -- N -- N   refs/heads/MPOM-431 (19c4ad7)

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:
 pom.xml | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)