elharo commented on code in PR #694:
URL: https://github.com/apache/maven-site/pull/694#discussion_r1965433430
##########
content/apt/guides/mini/guide-configuring-plugins.apt:
##########
@@ -47,7 +47,11 @@ 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 POM file, Maven uses the group ID
<<<org.apache.maven.plugins>>> to find the plugin.
+ 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>>>.
Review Comment:
I'd put commands line and in-POM usage into two separate and independent
paragraphs. As is, I had trouble following this.
##########
content/apt/guides/mini/guide-configuring-plugins.apt:
##########
@@ -47,7 +47,11 @@ 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 POM file, Maven uses the group ID
<<<org.apache.maven.plugins>>> to find the plugin.
Review Comment:
the POM file
delete "to find the plugin"
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
