From 2d0c1f4a6c470da7a7d13ba333737dfc715b9116 Mon Sep 17 00:00:00 2001
From: Robert Krajewski <rpk@alum.mit.edu>
Date: Wed, 1 Oct 2025 15:59:00 -0400
Subject: [PATCH] Document the banMavenDefaults option for the
 requirePluginVersions rule.

I did not link to the Super POM or default lifecycle bindings because
the pages are dependent on the version of Maven.

* https://maven.apache.org/ref/3.9.11/maven-model-builder/super-pom.html
* https://maven.apache.org/ref/3.9.11/maven-core/default-bindings.html

There's a mavenVersion property that could be used to replace a fixed
Maven version in these particular links if APT allows it, I suppose.
---
 enforcer-rules/src/site/apt/requirePluginVersions.apt.vm | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/enforcer-rules/src/site/apt/requirePluginVersions.apt.vm b/enforcer-rules/src/site/apt/requirePluginVersions.apt.vm
index 60bf472f..a47038b7 100644
--- a/enforcer-rules/src/site/apt/requirePluginVersions.apt.vm
+++ b/enforcer-rules/src/site/apt/requirePluginVersions.apt.vm
@@ -33,6 +33,15 @@ Require Plugin Versions
 
    * <<banLatest>> - disallow any use of "LATEST" as a version for any plugin. Default = true.
 
+   * <<banMavenDefaults>> -- require all plugin versions to be defined in the project;
+   the default is true. If false, the version of a plugin will be obtained from the
+   super POM or default lifecycle bindings. That is, a value of false will
+   free the project from having to define versions of many standard plugins, instead
+   delegating them to the version of Maven designed by the project's
+   {{{https://maven.apache.org/tools/wrapper/}Maven wrapper}}
+   or a version of Maven enforced by the
+   {{{./requireMavenVersion.html}requireMavenVersion}} rule.
+
    * <<banRelease>> - disallow any use of "RELEASE" as a version for any plugin. Default = true.
 
    * <<banSnapshots>> - disallow any use of SNAPSHOT plugins. Default = true.