This is an automated email from the ASF dual-hosted git repository.
slachiewicz pushed a change to branch next
in repository https://gitbox.apache.org/repos/asf/maven-rar-plugin.git.
discard 2818ab3 [MRAR-84] Bump maven-archiver to 3.5.1
discard 25baeea [MRAR-83] Bump plexus-archiver to 4.2.5
discard 98440bc Cleanup - Java 7 - replace with diamond
discard ddd25a4 Bump junit from 4.13.1 to 4.13.2
new 71b9219 [MRAR-80] Bump junit to 4.13.2
new fe4735f Cleanup - Java 7 - replace with diamond
new 1e5a2d3 [MRAR-83] Bump plexus-archiver to 4.2.5
new 3af5b4b [MRAR-84] Bump maven-archiver to 3.5.1
new 9289665 [MRAR-62] Bump maven-filtering to 3.2.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 (2818ab3)
\
N -- N -- N refs/heads/next (9289665)
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 5 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 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
