[
http://jira.codehaus.org/browse/MCHECKSTYLE-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210808#action_210808
]
Benjamin Bentmann commented on MCHECKSTYLE-131:
-----------------------------------------------
Out of curiosity, where did the plugin documentation state that one can use a
relative path like "checkstyle.xml" in the plugin configuration and have the
plugin resolve this to the parent's project instead of the current project as
the rest of Maven does?
IMHO, the example project is simply invalid, illustrated by the fact that it
fails to run "checkstyle:check" directly from the module directory. The proper
way to share the configuration in a multi-module build is documented in
[Multimodule
Configuration|http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/multi-module-config.html]
> Plugin can't use configLocation from parent.
> --------------------------------------------
>
> Key: MCHECKSTYLE-131
> URL: http://jira.codehaus.org/browse/MCHECKSTYLE-131
> Project: Maven 2.x Checkstyle Plugin
> Issue Type: Bug
> Affects Versions: 2.5
> Reporter: Frederic Müller
> Assignee: Olivier Lamy
> Priority: Critical
> Fix For: 2.6
>
> Attachments: example.zip
>
>
> Since Version 2.5 the checkstyle plugin no longer uses a configLocation that
> is located in the parent project but fails the build because of a missing
> resource.
> Version 2.4 is working as expected.
--
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
