[ http://jira.codehaus.org/browse/MCHECKSTYLE-31?page=all ]
Brett Porter updated MCHECKSTYLE-31:
------------------------------------
Fix Version: (was: 2.0)
2.1
> 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
> Fix For: 2.1
>
>
> 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
