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-pmd-plugin.git
discard cf49d3b [MPMD-390] Dynamically calculate xrefLocation/xrefTestLocation
discard 7ae5b1c [MPMD-389] Upgrade to Doxia 2.0.0 Milestone Stack
omit f822e83 [MPMD-395] Build doesn't fail for invalid CPD format
add 76f7e11 [MPMD-395] Build doesn't fail for invalid CPD format (#150)
add 872fcd8 [MPMD-397] Upgrade to Maven 3.6.3
add 570fe17 [maven-release-plugin] prepare release maven-pmd-plugin-3.23.0
add 1961d77 [maven-release-plugin] prepare for next development iteration
add 70fcdd0 Bump org.apache.maven.shared:maven-common-artifact-filters
add d54de0c [MPMD-389] Upgrade to Doxia 2.0.0 Milestone Stack
add c017d29 [MPMD-390] Dynamically calculate xrefLocation/xrefTestLocation
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 (cf49d3b)
\
N -- N -- N refs/heads/doxia-2.0.0 (c017d29)
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 | 34 +++++++++++++++++-----------------
1 file changed, 17 insertions(+), 17 deletions(-)
