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

Guillaume Boué closed MCHECKSTYLE-31.
-------------------------------------
    Resolution: Fixed

This is fixed since the Site plugin 3.0 (MSITE-444). You can declare 
dependencies in {{pluginManagement}} section and it will be inherited by report 
plugins like checkstyle.

> Multi-module reports do not support custom classpath configurations
> -------------------------------------------------------------------
>
>                 Key: MCHECKSTYLE-31
>                 URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-31
>             Project: Maven Checkstyle Plugin
>          Issue Type: Bug
>          Components: checkstyle:check, checkstyle:checkstyle
>    Affects Versions: 2.0-beta-1
>            Reporter: Mike Perham
>            Assignee: fabrizio giustina
>            Priority: Critical
>              Labels: maven-core
>
> The latest multi-module tip shows the following:
> {noformat}
> <reporting>
>     <plugins>
>       <plugin>
>         <groupId>org.apache.maven.plugins</groupId>
>         <artifactId>maven-checkstyle-plugin</artifactId>
>         <configuration>
>           <configLocation>whizbang/checkstyle.xml</configLocation>
>           <headerLocation>whizbang/LICENSE.txt</headerLocation>
>         </configuration>
>         <dependencies>
>           <dependency>
>             <groupId>com.example.whizbang</groupId>
>             <artifactId>build-tools</artifactId>
>             <version>1.0</version>
>           </dependency>
>         </dependencies>
>       </plugin>
>     </plugins>
>   </reporting>
> {noformat}
> This is invalid according to the latest 2.0.2 POM schema.  <dependencies> is 
> not supported in reporting plugins.
> So it seems impossible to provide a custom config in a multi-module build 
> without using a network URL as we cannot use File or classpath.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to