(maven-site) branch master updated: [MNGSITE-453] Document default groupId of plugins

[mb...@apache.org]

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

mbuenger pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-site.git


The following commit(s) were added to refs/heads/master by this push:
     new 1caea07f [MNGSITE-453] Document default groupId of plugins
1caea07f is described below

commit 1caea07fd660abacca025bf74f18f3c9db92f689
Author: Matthias Bünger <Bu...@users.noreply.github.com>
AuthorDate: Sat Feb 22 17:44:15 2025 +0100

    [MNGSITE-453] Document default groupId of plugins
---
 content/apt/guides/mini/guide-configuring-plugins.apt | 7 ++++++-
 content/apt/pom.apt.vm                                | 4 ++++
 2 files changed, 10 insertions(+), 1 deletion(-)

diff --git a/content/apt/guides/mini/guide-configuring-plugins.apt b/content/apt/guides/mini/guide-configuring-plugins.apt
index 64e09bc6..82247ae4 100644
--- a/content/apt/guides/mini/guide-configuring-plugins.apt
+++ b/content/apt/guides/mini/guide-configuring-plugins.apt
@@ -47,7 +47,12 @@ Guide to Configuring Plug-ins
   {{{/ref/current/maven-model/maven.html#class_plugin}information}}:
   <<<groupId>>>, <<<artifactId>>> and <<<version>>>.
 
-  <<Important Note>>: Always define the version of each plugin used to guarantee
+  If no <<<groupId>>> is defined for a plugin in the <<<build>>> or <<<reporting>>> section of the POM file, Maven uses the group ID <<<org.apache.maven.plugins>>>.
+  This means that Maven assumes an official Maven plugin will be used.
+
+  If a plugin is called from the command line without a fully qualified name, for example <<<mvn versions:set>>>, Maven searches for plugins with the group ID <<<org.apache.maven.plugins>>> or <<<org.codehaus.mojo>>>.
+
+  <<Important Note>>: Always define the version of each plugin to guarantee
   build reproducibility. A good practice is to specify each build plugin's version in a <<<\<build\>\<pluginManagement/\>\</build\>>>>
   element. Often the \<pluginManagement/\> element is found in the parent POM.
   For reporting plugins, specify each version in the <<<\<reporting\>\<plugins/\>\</reporting\>>>> element
diff --git a/content/apt/pom.apt.vm b/content/apt/pom.apt.vm
index 4516aaa8..1da1effe 100644
--- a/content/apt/pom.apt.vm
+++ b/content/apt/pom.apt.vm
@@ -983,6 +983,10 @@ Display parameters as parsed by Maven (in canonical form and as a list of tokens
 </project>
 +------------------------------------------+
 
+  Plugins are also identified by coordinates.
+  Unlike dependencies, there is a default <<<groupId>>> for plugins.
+  See {{{/guides/mini/guide-configuring-plugins.html}Configuring Plugins}}.
+
   Beyond the standard coordinate of <<<groupId:artifactId:version>>>, there are elements which
   configure the plugin or this builds interaction with it.