Look up Progmasoft's groups only in Progmasoft's repositorydocs/gradle-plugin-repository

The settings of the plugin example listed the Gradle Plugin Portal first
and filtered only the Progmasoft repository, so Gradle asked the Portal for
com.progmasoft.tazel.plugin before Progmasoft's own repository. The
example now makes https://maven.progmasoft.com/tazel exclusive for
com.progmasoft.tazel and its subgroups: Gradle resolves those there and
nowhere else, and every other plugin from the Portal.

The example builds as written: the Gradle plugin and tazel-api resolve
and jar writes the plugin JAR with its descriptor.

1 files changed, 7 insertions, 4 deletions

diff --git a/content/en-US/docs/3.extending/1.plugins.md b/content/en-US/docs/3.extending/1.plugins.md
index 5089adf..cadc750 100644
--- a/content/en-US/docs/3.extending/1.plugins.md
+++ b/content/en-US/docs/3.extending/1.plugins.md
@@ -52,16 +52,19 @@ command fails with `resolved plugins were not declared by the script`.
 
 A plugin is built with Gradle 9 and the Gradle plugin `com.progmasoft.tazel.plugin`, whose version is the version of
 Tazel the plugin is built for. Progmasoft publishes the Gradle plugin at `https://maven.progmasoft.com/tazel`, beside
-the API, so the settings of the build name that repository for plugins:
+the API, so the settings of the build name that repository for plugins. The repository is exclusive for the groups
+`com.progmasoft.tazel` and `com.progmasoft.tazel.*`: Gradle looks them up there and nowhere else, and looks up every
+other plugin, such as Kotlin's, in the Gradle Plugin Portal:
 
 ```kotlin
 // settings.gradle.kts of the plugin
 pluginManagement {
   repositories {
-    gradlePluginPortal()
-    maven("https://maven.progmasoft.com/tazel") {
-      content { includeGroupByRegex("com\\.progmasoft\\.tazel(\\..*)?") }
+    exclusiveContent {
+      forRepository { maven("https://maven.progmasoft.com/tazel") }
+      filter { includeGroupByRegex("com\\.progmasoft\\.tazel(\\..*)?") }
     }
+    gradlePluginPortal()
   }
 }