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 1a5279c [MPIR-462] IT for MRJAR issue with dependencies goal
discard 284f32f [MPIR-463] Remove workaround to count the number of root
content entries in JAR files
discard 6f3031f [MPIR-464] Upgrade to Maven Shared JAR 3.1.1
add 740536d Lift restriction on mojo renames
new 790b646 [MPIR-464] Upgrade to Maven Shared JAR 3.1.1
new 3fd654a [MPIR-463] Remove workaround to count the number of root
content entries in JAR files
new b707915 [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 (1a5279c)
\
N -- N -- N refs/heads/maven-shared-jar-3.1.1 (b707915)
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:
src/site/apt/index.apt.vm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
