You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2019/07/24 21:30:00 UTC

[jira] [Updated] (MNG-6540) Configuration in reporting section not taken into account when running from cli

     [ https://issues.apache.org/jira/browse/MNG-6540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov updated MNG-6540:
--------------------------------
    Fix Version/s: waiting-for-feedback

> Configuration in reporting section not taken into account when running from cli
> -------------------------------------------------------------------------------
>
>                 Key: MNG-6540
>                 URL: https://issues.apache.org/jira/browse/MNG-6540
>             Project: Maven
>          Issue Type: Bug
>    Affects Versions: 3.6.0
>            Reporter: Hans Aikema
>            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
(v7.6.14#76016)