Guillaume Boué created MSHARED-616:
--------------------------------------
Summary: Dependencies inside pluginManagement are not taken into
account in reporting
Key: MSHARED-616
URL: https://issues.apache.org/jira/browse/MSHARED-616
Project: Maven Shared Components
Issue Type: Bug
Components: maven-reporting-exec
Affects Versions: maven-reporting-exec-1.3
Reporter: Guillaume Boué
Assignee: Guillaume Boué
Fix For: maven-reporting-exec-1.4
When a reporting plugin is used, and that plugin is also present in a
{{pluginManagement}} section where custom {{dependencies}} are declared, those
dependencies are not used during site generation.
The issue was originally reported [on Stack
Overflow|http://stackoverflow.com/q/42121531/1743880]. Here's a minimal POM
showing the behaviour:
{code:xml}
<build>
<pluginManagement>
<plugins>
<plugin>
<artifactId>maven-checkstyle-plugin</artifactId>
<version>2.17</version>
<dependencies>
<dependency>
<groupId>com.puppycrawl.tools</groupId>
<artifactId>checkstyle</artifactId>
<version>7.5</version>
</dependency>
</dependencies>
</plugin>
</plugins>
</pluginManagement>
</build>
<reporting>
<plugins>
<plugin>
<artifactId>maven-checkstyle-plugin</artifactId>
<reportSets>
<reportSet>
<reports>
<report>checkstyle</report>
</reports>
</reportSet>
</reportSets>
</plugin>
</plugins>
</reporting>
{code}
When running {{mvn clean site}}, the Checkstyle Plugin, during site generation,
will incorrectly use the default Checkstyle 6.11.2, instead of the version 7.5
that was explicitly specified in the dependencies.
A work-around is to add an (empty) {{plugin}} declaration in
{{build.plugins.plugin}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
