[maven-enforcer] branch MENFORCER-389 updated (441a02f -> c700334)

[sj...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

sjaranowski pushed a change to branch MENFORCER-389
in repository https://gitbox.apache.org/repos/asf/maven-enforcer.git


    omit 441a02f  [MENFORCER-389] Allow filtering of parent in requireReleaseDeps
     add f087e8e  [MENFORCER-420] Cache the results of getDependenciesToCheck across rules.
     add 1f7751e  Bump assertj-core from 3.22.0 to 3.23.0
     add 02a416d  [MENFORCER-421] Use currently build artifacts in IT tests
     add c700334  [MENFORCER-389] Allow filtering of parent in requireReleaseDeps

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   (441a02f)
            \
             N -- N -- N   refs/heads/MENFORCER-389 (c700334)

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:
 .../maven/enforcer/rule/api/EnforcerRuleHelper.java      | 10 ++++++++++
 .../maven/plugins/enforcer/AbstractBanDependencies.java  | 16 ++++++++++++++--
 .../plugins/enforcer/DefaultEnforcementRuleHelper.java   | 13 +++++++++++++
 maven-enforcer-extension/pom.xml                         |  6 +++---
 maven-enforcer-plugin/pom.xml                            |  3 +++
 pom.xml                                                  |  2 +-
 6 files changed, 44 insertions(+), 6 deletions(-)