This is an automated email from the ASF dual-hosted git repository.
olamy pushed a change to branch mvn-3.9.1
in repository
https://gitbox.apache.org/repos/asf/maven-build-cache-extension.git
discard d0c677a [MBUILDCACHE-58] save remote not working anymore with Maven
3.9.1
discard f21c400 build with 3.9.1 and alpha-5
discard 18ce86d maven3 profile build
discard 176bdb7 change GH name
discard 90a308b Maven 3.9.1 test
add 15f9095 Bump logback-classic from 1.3.6 to 1.3.7
add ac3e95b [MBUILDCACHE-57] Configure remote url/remote server id with
command line property (#74)
add a7045bd Maven 3.9.1 test
add a122107 change GH name
add ba1514b maven3 profile build
add a5b16ff build with 3.9.1 and alpha-5
add bce68e3 [MBUILDCACHE-58] save remote not working anymore with Maven
3.9.1
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 (d0c677a)
\
N -- N -- N refs/heads/mvn-3.9.1 (bce68e3)
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 +-
.../maven/buildcache/xml/CacheConfigImpl.java | 6 ++-
src/site/markdown/parameters.md | 2 +
.../maven/buildcache/its/RemoteCacheDavTest.java | 48 +++++++++++++++++++---
4 files changed, 49 insertions(+), 9 deletions(-)
