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

hboutemy pushed a change to branch maven4-enabled
in repository https://gitbox.apache.org/repos/asf/maven-help-plugin.git


 discard 8816e7e  enable build with Maven 4
     add 1e716e1  Use version properties in IT (#368)
     add 4bd3786  enable build with Maven 4
     add f711a92  revert broken IT updates from #344

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   (8816e7e)
            \
             N -- N -- N   refs/heads/maven4-enabled (f711a92)

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                                                  |  3 +++
 .../projects/active-profiles_multimodule/verify.groovy   | 16 ++++------------
 src/it/projects/describe-cmd-with-goal-report/pom.xml    |  2 +-
 .../describe-plugin-in-plugin-management/pom.xml         |  2 +-
 .../describe-plugin-in-plugin-management/verify.groovy   |  2 +-
 src/it/projects/effective-pom_properties/verify.groovy   | 11 ++++-------
 6 files changed, 14 insertions(+), 22 deletions(-)

Reply via email to