This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/version.plantuml-maven-plugin-0.3
in repository https://gitbox.apache.org/repos/asf/maven-site.git
discard 1073ade3 Bump version.plantuml-maven-plugin from 0.2 to 0.3
add ec0e785d Injection and Mojo tests now use Guice (#585)
add a73dda07 javadoc plugin 3.11.2
add 4791699d [MNGSITE-546] Remove download.cgi and instead leverage the
global one (#589)
add 638cb2ef maven-changes-plugin 3.0.0-M1 released
add 8aa86abd Fluido Skin 2.0.1
add 27817a66 Use Fluido 2.0.1 (#591)
add 9b25d667 Bump version.plantuml-maven-plugin from 0.2 to 0.3
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 (1073ade3)
\
N -- N -- N
refs/heads/dependabot/maven/version.plantuml-maven-plugin-0.3 (9b25d667)
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:
content/apt/plugin-developers/plugin-testing.apt | 30 ++-
content/apt/plugins/index.apt | 4 +-
content/apt/skins/index.apt | 2 +-
content/resources/download.cgi | 4 -
.../xsd/{changes-1.0.0.xsd => changes-2.0.0.xsd} | 259 ++++++++-------------
pom.xml | 4 +-
6 files changed, 127 insertions(+), 176 deletions(-)
delete mode 100755 content/resources/download.cgi
copy content/resources/xsd/{changes-1.0.0.xsd => changes-2.0.0.xsd} (50%)
