This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/jettyVersion-9.4.22.v20191022
in repository https://gitbox.apache.org/repos/asf/maven-site-plugin.git.
omit ea2506a Bump jettyVersion from 9.2.28.v20190418 to 9.4.22.v20191022
add 19be00a MSITE-851 make output jars reproducible like m-source-p
add 89fd158 upgraded Jetty
add bf70be4 Bump jettyVersion from 9.2.28.v20190418 to 9.4.22.v20191022
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 (ea2506a)
\
N -- N -- N
refs/heads/dependabot/maven/jettyVersion-9.4.22.v20191022 (bf70be4)
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 | 8 ++++----
src/it/projects/site-jar/pom.xml | 1 +
src/it/projects/site-jar/verify.bsh | 5 +++++
.../apache/maven/plugins/site/render/SiteJarMojo.java | 16 +++++++++++++++-
4 files changed, 25 insertions(+), 5 deletions(-)
