[
https://issues.apache.org/jira/browse/MSHARED-831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17543793#comment-17543793
]
Hans Aikema commented on MSHARED-831:
-------------------------------------
[~hboutemy]
{quote}I have a question for [~aikebah]: do you really use mvn clean
project-info-reports:dependencies for serious use, instead of generating the
full site?
{quote}
It was the information in the docs that got me thinking there would be
something wrong in the code of the plugin. By using one of maven's own
reporting mojos I validated that the issue (reporting section configuration not
taken into account during direct-plugin-goal-invocation) was not isolated to
our plugin. That's the only reason why I had the
project-info-reports:dependencies as a direct invocation.
I see no reason to run a reporting-plugin configured in the reporting section
outside the maven site generation for serious use.
As for the cases where there might be a good reason I see no problem in then
having to move configuration to the build/plugins section to have it taken into
account in both direct-goal invocation and site generation.
I'm perfectly fine with closing this one as a wontfix (assuming that something
resembling a docsfixed resolution is not available, otherwise that would be
more appropriate in my view - the reported issue was solved by bringing the
docs in line with the actual implementation)
As a side-note: The new text needs a typo-fix in line 635
https://github.com/apache/maven-site/blob/b3db55e331c3070e79870f96196268a4d60ad208/content/apt/guides/mini/guide-configuring-plugins.apt#L635
`Sine` should be `Since`
> Configuration in reporting section not taken into account when running from
> cli
> -------------------------------------------------------------------------------
>
> Key: MSHARED-831
> URL: https://issues.apache.org/jira/browse/MSHARED-831
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-reporting-impl
> Affects Versions: maven-reporting-impl 3.0
> Reporter: Hans Aikema
> Assignee: Michael Osipov
> Priority: Major
> Fix For: waiting-for-feedback
>
>
> Investigating on [https://github.com/jeremylong/DependencyCheck/issues/1444]
> my conclusion is that plugin configuration using the reporting section does
> not work as documented on
> [https://maven.apache.org/guides/mini/guide-configuring-plugins.html#Using_the_reporting_Tag_VS_build_Tag]
> When configuring the plugin using the reporting section of the pom the
> configuration is not applied when calling the plugin goal from the CLI
> whereas the guide states that it is first looked up there and only when not
> found searched for in the build section.
> Don't know if this is the intended behaviour of the CLI-invocation of the
> plugins (and thus a documentation bug) or an actual bug in the configuration
> evaluation, but I spotted similar behaviour with the
> maven-project-info-reports-plugin
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
