This is an automated email from the ASF dual-hosted git repository.
slachiewicz pushed a change to branch INFRA-19861
in repository https://gitbox.apache.org/repos/asf/maven-site-plugin.git.
discard 26e2a8c [INFRA-19861] reduce combinations
add b2edd6f [MSITE-852] remove Struts dependencies with Doxia Site
Renderer to 1.9.2
add e802657 [maven-release-plugin] prepare release maven-site-plugin-3.9.0
add 048b89b [maven-release-plugin] prepare for next development iteration
add c51d7b5 remove info about old version (#19)
add 45d6256 Bump junit from 4.8.1 to 4.13
add af15e83 uodate test dependencies (#17)
add 4350177 Only reference current version (#18)
add bf68470 assume Maven 3 as default (#20)
new 73e7069 [INFRA-19861] reduce combinations
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 (26e2a8c)
\
N -- N -- N refs/heads/INFRA-19861 (73e7069)
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 | 10 +-
src/site/apt/index.apt.vm | 11 +-
src/site/apt/maven-3.apt.vm | 361 --------------------------------------------
src/site/site.xml | 1 -
4 files changed, 9 insertions(+), 374 deletions(-)
delete mode 100644 src/site/apt/maven-3.apt.vm
