This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/com.google.guava-guava-33.2.0-jre
in repository https://gitbox.apache.org/repos/asf/maven-mvnd.git
discard 5b616c9c Bump com.google.guava:guava from 32.1.3-jre to 33.2.0-jre
add 907c9e76 Bump io.takari.maven:takari-smart-builder from 0.6.5 to 0.6.6
(#986)
add 66295264 Bump maven.plugin-tools.version from 3.12.0 to 3.13.0 (#987)
add 224f6a56 Bump ca.vanzyl.provisio.maven.plugins:provisio-maven-plugin
add 7939f993 Bump org.apache.maven.plugins:maven-wrapper-plugin from 3.3.0
to 3.3.1
add f3e6cbf9 Revert "Bump org.apache.maven.plugins:maven-wrapper-plugin
from 3.3.0 to 3.3.1"
add 8434b80f Revert "Bump
ca.vanzyl.provisio.maven.plugins:provisio-maven-plugin"
add b6e46908 Maven 4 beta-2 (#998)
add 9e3f2e43 Bump com.google.guava:guava from 32.1.3-jre to 33.2.0-jre
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 (5b616c9c)
\
N -- N -- N
refs/heads/dependabot/maven/com.google.guava-guava-33.2.0-jre (9e3f2e43)
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:
.mvn/wrapper/maven-wrapper.properties | 3 ++-
build-plugin/pom.xml | 2 +-
.../java/org/apache/maven/cli/DaemonMavenCli.java | 10 ++++++++
logging/pom.xml | 3 +--
mvnw | 4 +--
mvnw.cmd | 2 +-
pom.xml | 29 ++++++++++++++++------
7 files changed, 39 insertions(+), 14 deletions(-)
