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

slachiewicz pushed a change to branch use-latest-mvn4
in repository https://gitbox.apache.org/repos/asf/maven-compiler-plugin.git


    omit 10235b0  use latest Maven 4
     add ddbb0e7  Bump org.ow2.asm:asm from 9.9.1 to 9.10
     add ffbc13e  Fix ITs for Maven 3.10.x
     add c7c9011  Bump org.ow2.asm:asm from 9.10 to 9.10.1
     add 5906dd4  Bump mavenVersion from 3.9.14 to 3.9.16
     add c44d3cb  Bump org.apache.maven.plugins:maven-plugins from 47 to 48
     add 26277aa  use latest 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   (10235b0)
            \
             N -- N -- N   refs/heads/use-latest-mvn4 (26277aa)

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                                            |  6 ++--
 .../.mvn/maven.config}                             | 36 +++++++++++-----------
 2 files changed, 21 insertions(+), 21 deletions(-)
 copy src/it/{MCOMPILER-129/invoker.properties => 
MCOMPILER-346/.mvn/maven.config} (90%)

Reply via email to