This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/org.apache.maven-maven-core-3.8.1
in repository https://gitbox.apache.org/repos/asf/maven-reporting-exec.git
discard 0394d19 Bump org.apache.maven:maven-core from 3.2.5 to 3.8.1
add 55262ef [MSHARED-1362] Upgrade plugins and components (in ITs)
add c9ee1d1 Put project.build.outputTimestamp last
add f6729a7 [maven-release-plugin] prepare release
maven-reporting-exec-2.0.0-M13
add c5ea890 [maven-release-plugin] prepare for next development iteration
add 2cd21f6 [MSHARED-1392] Upgrade to Parent 42 and Maven 3.6.3
add fc917f8 Bump org.apache.maven:maven-core from 3.2.5 to 3.8.1
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 (0394d19)
\
N -- N -- N
refs/heads/dependabot/maven/org.apache.maven-maven-core-3.8.1 (fc917f8)
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 | 52 +++++++++++++---------
src/it/reportConfig/pom.xml | 2 +-
.../exec/TestDefaultMavenReportExecutor.java | 42 ++++++++++-------
3 files changed, 59 insertions(+), 37 deletions(-)
