This is an automated email from the ASF dual-hosted git repository. khmarbaise pushed a change to branch MPOM-207 in repository https://gitbox.apache.org/repos/asf/maven-apache-parent.git.
discard d4b0402 [MPOM-207] - Upgrade maven-compiler-plugin to version 3.8.0 add bc91125 improved documentation of source-release-assembly add d4d7924 MPOM-209. Correct Jira URL. add cc8b502 [MPOM-208] update scm-api also since it has changed add 8e34dc5 [MPOM-196] Update maven-assembly-plugin to 3.1.1 add f4bfc53 [MPOM-219] upgraded m-help-p to 3.2.0 (for verbose effective-pom) add da59750 prepare to publish documentation for 22-SNAPSHOT add d9bdadd [MPOM-220] Update link to ASF logo new a4cf226 [MPOM-207] - Upgrade maven-compiler-plugin to version 3.8.0 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 (d4b0402) \ N -- N -- N refs/heads/MPOM-207 (a4cf226) 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 | 18 ++++++++++++++---- site-pom.xml | 4 ++-- src/site-docs/apt/index.apt.vm | 8 +++++--- 3 files changed, 21 insertions(+), 9 deletions(-)