This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/com.thoughtworks.xstream-xstream-1.4.21
in repository https://gitbox.apache.org/repos/asf/maven-mvnd.git
discard c7097552 Bump com.thoughtworks.xstream:xstream from 1.4.20 to 1.4.21
add 7726c16b fix: Daemon invoker lifespan must be shared with daemon
process lifespan (#1196)
add a08cd297 Bump org.apache.maven.plugins:maven-site-plugin from 3.20.0
to 3.21.0 (#1180)
add 32cf0ef0 Bump testcontainers.version from 1.20.2 to 1.20.3 (#1182)
add e03959b1 Bump maven.plugin-tools.version from 3.15.0 to 3.15.1 (#1184)
add fe8a1504 Bump com.thoughtworks.xstream:xstream from 1.4.20 to 1.4.21
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 (c7097552)
\
N -- N -- N
refs/heads/dependabot/maven/com.thoughtworks.xstream-xstream-1.4.21 (fe8a1504)
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:
.../main/java/org/apache/maven/cli/DaemonCli.java | 2 +-
.../org/apache/maven/cli/DaemonMavenCling.java | 52 ++++++++++++++--------
.../org/apache/maven/cli/DaemonMavenInvoker.java | 18 ++++++--
.../java/org/mvndaemon/mvnd/daemon/Server.java | 6 ++-
pom.xml | 6 +--
5 files changed, 57 insertions(+), 27 deletions(-)
