kwin commented on pull request #31:
URL: 
https://github.com/apache/maven-apache-parent/pull/31#issuecomment-755266020


   > the question of configuring the reporting section in addition to 
configuring the plugin, which should not be necessary if pluginManagement is 
configured since maven-site-plugin 3.4: see 
https://maven.apache.org/plugins/maven-site-plugin/history.html (some 
documentation here and there should probably require some updates to explain 
how things evolved over time)
   
   On that page, I could not find hints, also the link 
https://maven.apache.org/plugins/maven-site-plugin/maven-3.html is dead on that 
page. The only references towards build plugin/reference plugin configuration is
   
   1. https://maven.apache.org/pom.html#reporting, stating 
       > And the subtler difference is that a plugin configuration under the 
reporting element works as build plugin configuration, although the opposite is 
not true (a build plugin configuration does not affect a reporting plugin).
   
       This information lead me to believe that also build plugin Management 
would not affect reporting plugins. This requires clarification.
   
   1. 
https://maven.apache.org/guides/mini/guide-configuring-plugins.html#using-the-reporting-tag-vs-build-tag,
 stating 
       > 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>.
   
       This also indicates that plugin management is not relevant for reporting 
plugins, as the `only` is in printed in bold
   
   There is also the related bug report about Maven not behaving as documented: 
https://issues.apache.org/jira/browse/MNG-7006.
   Please clarify first what is the intended behaviour, because right now I am 
totally lost with what is desired behaviour vs. what is actually a bug.


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Reply via email to