This is an automated email from the ASF dual-hosted git repository.
michaelo pushed a change to branch doxia-2.0.0
in repository
https://gitbox.apache.org/repos/asf/maven-project-info-reports-plugin.git
discard 48ee168 [MPIR-454] Upgrade to Doxia 2.0.0 Milestone Stack
add 73658c3 Remove outdated invoker conditions
add 67ecd33 [MPIR-466] ModulesReport/IndexReport do not pass a complete
building request to renderer
add a917abe [maven-release-plugin] prepare release
maven-project-info-reports-plugin-3.6.2
add 8813fea [maven-release-plugin] prepare for next development iteration
new 290c168 [MPIR-454] Upgrade to Doxia 2.0.0 Milestone Stack
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 (48ee168)
\
N -- N -- N refs/heads/doxia-2.0.0 (290c168)
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 | 4 ++--
src/it/MPIR-300/invoker.properties | 5 ++---
src/it/MPIR-349/parent/invoker.properties | 5 ++---
.../org/apache/maven/report/projectinfo/IndexReport.java | 15 ++++++++++++++-
.../apache/maven/report/projectinfo/ModulesReport.java | 7 ++++++-
5 files changed, 26 insertions(+), 10 deletions(-)
