This is an automated email from the ASF dual-hosted git repository.
hboutemy 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 b3db55e3 [MSHARED-831] update documentation: what was true 13 years
ago is not any more
b3db55e3 is described below
commit b3db55e331c3070e79870f96196268a4d60ad208
Author: Hervé Boutemy <[email protected]>
AuthorDate: Sat May 28 18:31:26 2022 +0200
[MSHARED-831] update documentation: what was true 13 years ago is not
any more
---
content/apt/guides/mini/guide-configuring-plugins.apt | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/content/apt/guides/mini/guide-configuring-plugins.apt
b/content/apt/guides/mini/guide-configuring-plugins.apt
index 9a222ead..26888cf7 100644
--- a/content/apt/guides/mini/guide-configuring-plugins.apt
+++ b/content/apt/guides/mini/guide-configuring-plugins.apt
@@ -630,15 +630,15 @@ mvn myqyeryplugin:queryMojo@execution1
** {Using the <<<\<reporting\>>>> Tag VS <<<\<build\>>>> Tag}
- Configuring a reporting plugin in the \<reporting\> or \<build\> elements in
the pom does <<NOT>> have the same behavior!
+ Configuring a reporting plugin in the \<reporting\> or \<build\> elements in
the pom does not exactly have the same results.
- [<<<mvn site>>>] It uses <<only>> the parameters defined in the
\<configuration\> element of each reporting Plugin
- specified in the \<reporting\> element, i.e. <<<site>>> always <<ignores>>
the parameters defined in the
- \<configuration\> element of each plugin specified in \<build\>.
+ [<<<mvn site>>>] Sine maven-site-plugin 3.4, it uses the parameters defined
in the \<configuration\> element of each reporting Plugin
+ specified in the \<reporting\> element, in addition to the parameters
defined in the
+ \<configuration\> element of each plugin specified in \<build\> (parameters
from \<build\> section were previously ignored).
- [<<<mvn aplugin:areportgoal>>>] It uses <<firstly>> the parameters defined
in the \<configuration\> element of each
- reporting Plugin specified in the \<reporting\> element; if a parameter is
not found, it will look up to a parameter
- defined in the \<configuration\> element of each plugin specified in
\<build\>.
+ [<<<mvn aplugin:areportgoal>>>] It <<ignores>> the parameters defined in the
\<configuration\> element of each
+ reporting Plugin specified in the \<reporting\> element; only parameters
+ defined in the \<configuration\> element of each plugin specified in
\<build\> are used.
[]