[ http://jira.codehaus.org/browse/MCHECKSTYLE-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89430 ]
Christian Goetze commented on MCHECKSTYLE-31: --------------------------------------------- I've been trying to get this to work for some time, and I can't seem to get there... So I did move the plugin configuration into the <build /> section, which at least caused the cyclic dependency error I saw before (when I used <extensions /> to go away, but now it seems that it won't go more than one level deep, skipping over module directories that do not contain a src subtree. INFO] ---------------------------------------------------------------------------- [INFO] Building SenSage shared artifacts [INFO] task-segment: [checkstyle:check] [INFO] ---------------------------------------------------------------------------- [INFO] Preparing checkstyle:check [INFO] [checkstyle:checkstyle] [INFO] Source directory does not exist - skipping report. [INFO] [checkstyle:check] [INFO] Unable to perform checkstyle:check, unable to find checkstyle:checkstyle outputFile. This is using maven 2.0.5 > 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 > Issue Type: Bug > Affects Versions: 2.0-beta-1 > Reporter: Mike Perham > Assigned To: 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