[jira] Commented: (MCHECKSTYLE-31) Multi-module reports do not support custom classpath configurations

["John Allen (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MCHECKSTYLE-31?page=comments#action_65653 ] 

John Allen commented on MCHECKSTYLE-31:
---------------------------------------

Until core gets reporting sorted (ie. reportingManagement, dependencies for reports, etc) we define the checkstyle, clover-2.0 and pmd plugins as <build> plugins and specify their dependencies in the nornmal plugin way. Fortunately they dont have default goals bound to the lifecycle so don't do any harm in the normal biuld but when the report or check mojos are invoked either by site or via explicit invocation the plugin configuration seems to inherit the <build> defined configuration, including its dependencies.

> Multi-module reports do not support custom classpath configurations
> -------------------------------------------------------------------
>
>          Key: MCHECKSTYLE-31
>          URL: http://jira.codehaus.org/browse/MCHECKSTYLE-31
>      Project: Maven 2.x Checkstyle Plugin
>         Type: Bug

>     Versions: 2.0-beta-1
>     Reporter: Mike Perham
>     Assignee: fabrizio giustina
>     Priority: Critical

>
>
> 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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira