This is an automated email from the ASF dual-hosted git repository.
gnodet pushed a change to branch MNG-7129-3.8.x
in repository https://gitbox.apache.org/repos/asf/maven.git.
discard 75f9a45 Flag the method as deprecated as it will be moved to private
scope
discard 4ca2fb6 [MNG-7129] Necessary changes to support maven-caching
add 5bc395f Add github checks to maven-3.8.x branch
add 90373f0 [MNG-7129] Necessary changes to support maven-caching
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 (75f9a45)
\
N -- N -- N refs/heads/MNG-7129-3.8.x (90373f0)
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:
.github/workflows/maven.yml | 147 +++++++++++++++++++++
.../maven/lifecycle/internal/MojoExecutor.java | 6 +-
2 files changed, 148 insertions(+), 5 deletions(-)
create mode 100644 .github/workflows/maven.yml
