This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/org.junit.jupiter-junit-jupiter-engine-5.9.3
in repository
https://gitbox.apache.org/repos/asf/maven-build-cache-extension.git
discard c2c58c9 Bump junit-jupiter-engine from 5.9.2 to 5.9.3
add 72024fc add some log when saving file locally as nothing is displayed
if this has been done or not (#75)
add 0410dc4 fix issue introduced by
https://github.com/apache/maven-build-cache-extension/commit/ac3e95ba3772142ad81205ab26ea4460c4348ba1
remote enabled does not check property
add 0461afd Bump junit-jupiter-params from 5.9.2 to 5.9.3
add 7fe0247 Bump junit-jupiter-engine from 5.9.2 to 5.9.3
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 (c2c58c9)
\
N -- N -- N
refs/heads/dependabot/maven/org.junit.jupiter-junit-jupiter-engine-5.9.3
(7fe0247)
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 | 2 +-
.../org/apache/maven/buildcache/LocalCacheRepositoryImpl.java | 9 ++++-----
.../java/org/apache/maven/buildcache/xml/CacheConfigImpl.java | 2 +-
3 files changed, 6 insertions(+), 7 deletions(-)
