This is an automated email from the ASF dual-hosted git repository.
michaelo pushed a change to branch maven-shared-jar-3.1.1
in repository
https://gitbox.apache.org/repos/asf/maven-project-info-reports-plugin.git
discard 4336a4f [MPIR-462] IT for MR-jar troubling :dependencies goal
discard 866684c maven-shared-jar-3.1.1
add b08af0c Improve variable name
add 870d7bf Improve variable name (2)
add 9ba89c9 Fix SCM tag
new 652d461 [MPIR-464] Upgrade to Maven Shared JAR 3.1.1
new be549e9 [MPIR-463] Remove workaround to count the number of root
content entries in JAR files
new 46602c2 [MPIR-462] IT for MRJAR issue with dependencies goal
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 (4336a4f)
\
N -- N -- N refs/heads/maven-shared-jar-3.1.1 (46602c2)
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 3 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 | 8 ++------
1 file changed, 2 insertions(+), 6 deletions(-)
