Maven Checkstyle Plugin
  1. Maven Checkstyle Plugin
  2. MCHECKSTYLE-31

Multi-module reports do not support custom classpath configurations

    Details

    • Type: Bug Bug
    • Status: Reopened Reopened
    • Priority: Critical Critical
    • Resolution: Unresolved
    • Affects Version/s: 2.0-beta-1
    • Fix Version/s: None
    • Labels:
    • Number of attachments :
      0

      Description

      The latest multi-module tip shows the following:

      <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>
      

      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.

        Issue Links

          Activity

          No work has yet been logged on this issue.

            People

            • Assignee:
              fabrizio giustina
              Reporter:
              Mike Perham
            • Votes:
              2 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated: