This is an automated email from the ASF dual-hosted git repository.
khmarbaise pushed a change to branch MSHARED-731
in repository https://gitbox.apache.org/repos/asf/maven-archiver.git.
discard a4c4443 [MSHARED-731] - Upgrade plexus-archiver to 3.6.0
add 0164db6 [MSHARED-727] - Upgrade mave-surefire/failsafe-plugin 2.21.0
add 9111b94 Fixed Unit test.
add b2e0194 @Ignore test which looks like a JDK bug.
add 162e36c [MSHARED-747] - Upgrade maven-plugins parent to version 32
add 632597d [MNGSITE-341] use https for sigs, hashes and KEYS
add cba663c [MPOM-205] use sha512 checksums instead of sha1
new df3b76a [MSHARED-731] - Upgrade plexus-archiver to 3.6.0
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 (a4c4443)
\
N -- N -- N refs/heads/MSHARED-731 (df3b76a)
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.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
pom.xml | 18 +-----------
src/site/xdoc/download.xml.vm | 6 ++--
.../apache/maven/archiver/MavenArchiverTest.java | 34 +++++++++++++++-------
3 files changed, 27 insertions(+), 31 deletions(-)
