This is an automated email from the ASF dual-hosted git repository.
slachiewicz pushed a change to branch mvn4build
in repository https://gitbox.apache.org/repos/asf/maven-jar-plugin.git
discard b5859f4 Enable Maven 4 build in GitHub Actions workflow
add b28cf10 MJAR: Fix NullPointerException in AbstractJarMojo by
increasing field visibility and adding fallbacks
add f631e64 MJAR: Increase visibility of @Inject fields to protected to
ensure proper injection in Maven 4
new 6454c11 Enable Maven 4 build in GitHub Actions workflow
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 (b5859f4)
\
N -- N -- N refs/heads/mvn4build (6454c11)
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:
.../apache/maven/plugins/jar/AbstractJarMojo.java | 40 +++++++++++++---------
1 file changed, 23 insertions(+), 17 deletions(-)
