This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/org.codehaus.mojo-mrm-maven-plugin-1.6.0
in repository https://gitbox.apache.org/repos/asf/maven-site-plugin.git
discard ec41a71b Bump org.codehaus.mojo:mrm-maven-plugin from 1.5.0 to 1.6.0
add a157124f [MSITE-991] Upgrade to Parent 41
add 952ef111 [MSITE-993] Upgrade to Maven Reporting API 4.0.0-M9
add 90797338 [MSITE-994] Upgrade to Maven Reporting Exec 4.0.0-M12
add 87aeeb5f [MSITE-992] Upgrade to Doxia Sitetools 2.0.0-M16
add fea50671 [MSITE-995] Upgrade plugins and components (in ITs)
add 8ceb7b02 [MSITE-987] Consistently log when skipping report goal
execution
add 9d72298c Bump org.codehaus.mojo:mrm-maven-plugin from 1.5.0 to 1.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 (ec41a71b)
\
N -- N -- N
refs/heads/dependabot/maven/org.codehaus.mojo-mrm-maven-plugin-1.6.0 (9d72298c)
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 | 34 ++++++++++++----------
.../site/render/AbstractSiteRenderingMojo.java | 4 ++-
2 files changed, 21 insertions(+), 17 deletions(-)
