This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/org.apache.maven.plugins-maven-plugins-43
in repository https://gitbox.apache.org/repos/asf/maven-resources-plugin.git
omit 2181792 Bump org.apache.maven.plugins:maven-plugins from 42 to 43
add 6962075 use new Reproducible Central badge endpoint
add 3fdf055 [MRESOURCES-299] Be more accurate on using filtering element
(#81)
add b612259 Upgrade to Maven 4.0.0-beta-5 (#83)
add 3d2fc8f Update custom filters docs (#86)
add 2ede68f [MNGSITE-529] Rename "Goals" to "Plugin Documentation"
add b609103 Second person (#85)
add 6665efe [MRESOURCES-314] Upgrade to Maven 4.0.0-rc-2 (#87)
add 54da032 Bump org.apache.maven.plugins:maven-plugins from 42 to 43
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 (2181792)
\
N -- N -- N
refs/heads/dependabot/maven/org.apache.maven.plugins-maven-plugins-43 (54da032)
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-verify.yml | 4 +--
README.md | 2 +-
pom.xml | 11 +++---
.../apt/examples/custom-resource-filters.apt.vm | 42 ++++++----------------
src/site/apt/examples/filter.apt | 30 ++++++++--------
src/site/site.xml | 2 +-
6 files changed, 35 insertions(+), 56 deletions(-)
