This is an automated email from the ASF dual-hosted git repository.
dependabot[bot] pushed a change to branch
dependabot/maven/src/it/automodules-application/org.codehaus.plexus-plexus-utils-3.6.1
in repository https://gitbox.apache.org/repos/asf/maven-compiler-plugin.git
discard dca0fbd Bump org.codehaus.plexus:plexus-utils in
/src/it/automodules-application
add b8ada81 Bump org.apache.maven.plugins:maven-plugins from 47 to 48
add e8398ea Spotless
add 937e89c docs: Upgrade HTTP urls to HTTPS in documentation
add 43d82a6 Bump org.codehaus.plexus:plexus-utils in
/src/it/automodules-application
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 (dca0fbd)
\
N -- N -- N
refs/heads/dependabot/maven/src/it/automodules-application/org.codehaus.plexus-plexus-utils-3.6.1
(43d82a6)
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:
README.md | 2 +-
pom.xml | 2 +-
.../org/apache/maven/plugin/compiler/AbstractCompilerMojo.java | 8 +++++---
src/site/markdown/examples/compile-using-different-jdk.md | 8 ++++----
src/site/markdown/examples/set-compiler-source-and-target.md | 2 +-
src/site/markdown/index.md | 2 +-
src/site/markdown/multirelease.md | 2 +-
7 files changed, 14 insertions(+), 12 deletions(-)
