This is an automated email from the ASF dual-hosted git repository.
slachiewicz pushed a change to branch jd
in repository https://gitbox.apache.org/repos/asf/maven-jar-plugin.git
discard 3e02d54 Merge branch 'master' into jd
discard 55fabd1 retrigger checks
discard 0926ace Fix javadoc
add db9e2ae Bump org.codehaus.plexus:plexus-archiver from 4.10.4 to 4.11.0
add acfc912 Bump org.apache.maven.plugins:maven-plugins from 45 to 47
add 86eee28 Bump org.junit:junit-bom from 5.14.1 to 5.14.4
add 7c6ea2d Bump org.apache.maven.plugins:maven-plugins from 47 to 48
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
add 2780908 Bump org.codehaus.plexus:plexus-archiver from 4.11.0 to 4.12.0
add 03a2b66 Bump com.google.guava:guava from 33.5.0-jre to 33.6.0-jre
add c2738a9 Fix javadoc
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 (3e02d54)
\
N -- N -- N refs/heads/jd (c2738a9)
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 | 8 ++---
.../apache/maven/plugins/jar/AbstractJarMojo.java | 40 +++++++++++++---------
2 files changed, 27 insertions(+), 21 deletions(-)
