This is an automated email from the ASF dual-hosted git repository.
bmarwell pushed a change to branch MNGSITE-503_security.txt
in repository https://gitbox.apache.org/repos/asf/maven-site.git
omit 2ca7b80c [MNGSITE-503] set time to midnight, UTC; remove link to CVE
list (not a policy).
omit 9b296ca1 Update pom.xml
omit 847424b1 Monkey patch for Locale#ROOT
omit 350e7ab3 [MNGSITE-503] add .well-known/security.txt
add e66f6ed8 Add link to shared-resources with code style formatters (#350)
add 1dd8f71f do not use anymore withMaven
add 5bebb5cb add -ntp option
add 4a156c54 [INFRA] add autolink refs (#353)
add 0cca5772 Fix missing a space on paragraph
add b7ee8d3e [MNGSITE-503] add .well-known/security.txt
add c633df77 Monkey patch for Locale#ROOT
add 5a9536d2 Update pom.xml
add c6bb3754 [MNGSITE-503] set time to midnight, UTC; remove link to CVE
list (not a policy).
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 (2ca7b80c)
\
N -- N -- N refs/heads/MNGSITE-503_security.txt (c6bb3754)
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:
.asf.yaml | 22 ++++++++++++++++++++++
Jenkinsfile | 24 +++++++++---------------
content/apt/developers/conventions/code.apt | 4 ++++
3 files changed, 35 insertions(+), 15 deletions(-)
