[jira] Commented: (MCHECKSTYLE-31) Multi-module reports do not support custom classpath configurations
[
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 section, which at
least caused the cyclic dependency error I saw before (when I used 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}
>
>
>
> org.apache.maven.plugins
> maven-checkstyle-plugin
>
> whizbang/checkstyle.xml
> whizbang/LICENSE.txt
>
>
>
> com.example.whizbang
> build-tools
> 1.0
>
>
>
>
>
> {noformat}
> This is invalid according to the latest 2.0.2 POM schema. 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
[jira] Commented: (MCHECKSTYLE-31) Multi-module reports do not support custom classpath configurations
[ 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
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
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}
>
>
>
> org.apache.maven.plugins
> maven-checkstyle-plugin
>
> whizbang/checkstyle.xml
> whizbang/LICENSE.txt
>
>
>
> com.example.whizbang
> build-tools
> 1.0
>
>
>
>
>
> {noformat}
> This is invalid according to the latest 2.0.2 POM schema. 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
