3.2.0 Backported Issues

- requireReleaseDeps does not support optional dependencies or runtime scope #null
- show rules processed #null
- Enforcer 3.0.0 breaks with Maven 3.8.4 #null
- Violation messages can be really hard to find in a multi module project #null
- Maven enforcer rule which checks that all dependencies in dependencyManagement don't have an explicit scope set #null
- Clarify class loading for custom Enforcer rules #null
- Using junit jupiter bom instead of single artifacts. #null
- Allow one of many files in RequireFiles rules to pass #null
- Version 3.1.0 is not enforcing bannedDependencies rules #null
- Get rid of maven-dependency-tree dependency #null
- Upgrade maven-plugin parent to 38 #null
- Allow 8 as JDK version for requireJavaVersion #null
- Improve error message for rule "requireJavaVersion" #null
- Include Java Home in Message for Java Rule Failures #null
- Upgrade parent to version 39 #null
- Bump mrm-maven-plugin from 1.3.0 to 1.5.0 #null
- allow no rules #null
- DependencyConvergence should support including/excluding certain dependencies #null
- Support declaring external banned dependencies in an external file/URL #null
- Skip specific rules #null
- Bump maven-common-artifact-filters from 3.2.0 to 3.3.2 #null
- Bump Mockito from 4.6.1 to 4.11.0 #null
- Bump plexus-utils from 3.4.2 to 3.5.0 #null
- Verify working with Maven 4 #null
- Maven enforcer rule which checks that all dependencies have an explicit scope set #null
- Upgrade maven-plugin parent to 37 #null
- New Enforcer API #null
- New Enforcer API - RuleConfigProvider #null
- Rule for no version ranges, version placeholders or SNAPSHOT versions #null
- Deprecate display-info mojo #null
- DependencyConvergence treats provided dependencies are runtime dependencies #null
- Refresh download page #null
- Bump junit-bom from 5.9.0 to 5.9.1 #null
- Mange rules configuration by plugin #null
- Code cleanup #null
- Deprecate 'rules' property and introduce 'enforcer.rules' as a replacement #null
- Move Built-In Rules to new API #null
- Bump assertj-core from 3.23.1 to 3.24.2 #null
- Plugin shouldn't use NullPointerException for non-exceptional code flow #null
- Manage all Maven Core dependencies as provided #null

This issue is a tracking list of many backported items rather than a single change, and it names no files, tests, or entry points. Start by selecting one listed item and locating its corresponding issue; confirm its scope and acceptance criteria there before making any change. Done would require completing that item and validating its related tests.

Written by the indexing model from the issue text.