[
https://issues.apache.org/jira/browse/MNG-6540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16725332#comment-16725332
]
Hans Aikema commented on MNG-6540:
----------------------------------
Whereas no dependencies report is created when called with *mvn clean
project-info-reports:dependencies* for
{code:java}
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>net.aikebah</groupId>
<artifactId>mng6540-faulty</artifactId>
<version>1.0-SNAPSHOT</version>
<name>mng6540-faulty</name>
<dependencies>
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-api</artifactId>
<version>1.7.7</version>
</dependency>
</dependencies>
<build>
<pluginManagement>
<plugins>
<plugin>
<artifactId>maven-project-info-reports-plugin</artifactId>
<version>3.0.0</version>
<configuration>
<skip>true</skip>
</configuration>
</plugin>
</plugins>
</pluginManagement>
</build>
<reporting>
<plugins>
<plugin>
<artifactId>maven-project-info-reports-plugin</artifactId>
<version>3.0.0</version>
</plugin>
</plugins>
</reporting>
</project>
{code}
> 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
>
> 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.3#76005)