[
https://issues.apache.org/jira/browse/MNG-6540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16892478#comment-16892478
]
Hervé Boutemy edited comment on MNG-6540 at 7/25/19 7:07 AM:
-------------------------------------------------------------
thank you Michael for pinging me
it's an edge case (AFAIK not explicited anywhere): when you launch "mvn
project-info-reports:dependencies", you don't really launch a report from a
Maven perspective
you're launching a goal
a report is something launched by site plugin: and site plugin mimics normal
plugins behavour (through maven-report-exec
https://maven.apache.org/shared/maven-reporting-exec/ )
then defining the configuration in pluginManagement is perfectly taken into
account both by Maven (as a normal goal) and by maven-site-plugin (as a report)
but defining the configuration in reporting section is only taken into account
by maven-site-plugin: for Maven, it's a goal, not a report (even if this goal
simulates site plugin to generate a report)
the code for a goal to "simulate site plugin to generate a report" is
maven-reporting-impl: https://maven.apache.org/shared/maven-reporting-impl/
it could perhaps be enhanced to better simulate site plugin: this is where the
improvement should be
I propose to move this issue into maven-reporting-impl
and for the mini-guide, perhaps it's not consistent with real behaviour and
should be updated: this one is for MNGSITE
was (Author: hboutemy):
thank you Michael for pinging me
it's an edge case (AFAIK not explicited anywhere): when you launch "mvn
project-info-reports:dependencies", you don't really launch a report from a
Maven perspective
you're launching a goal
a report is something launched by site plugin: and site plugin mimics normal
plugins behavour (through maven-report-exec
https://maven.apache.org/shared/maven-reporting-exec/ )
then defining the configuration in pluginManagement is perfectly taken into
account both by Maven (as a normal goal) and by maven-site-plugin (as a report)
but defining the configuration in reporting section is only taken into account
by maven-site-plugin: for Maven, it's a goal, not a report (even if this goal
simulates site plugin to generate a report)
the code for a goal to "simulate site plugin to generate a report" is
maven-reporting-impl: https://maven.apache.org/shared/maven-reporting-impl/
it could perhaps be enhanced to better simulate site plugin: this is where the
improvement should be
I propose to move this issue into maven-reporting-impl
> 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.0, 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)
