[
https://issues.apache.org/jira/browse/MSHARED-831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17602242#comment-17602242
]
Hudson commented on MSHARED-831:
--------------------------------
Build succeeded in Jenkins: Maven » Maven TLP » maven-site » PR-287 #35
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-site/job/PR-287/35/
> 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
>
> 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.10#820010)
