[jira] (MCHECKSTYLE-184) Allow src/main/resources to be searched by Checkstyle

["Zlika (JIRA)" <ji...@codehaus.org>]

    [ https://jira.codehaus.org/browse/MCHECKSTYLE-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=326613#comment-326613 ] 

Zlika commented on MCHECKSTYLE-184:
-----------------------------------

Inclusion of *.properties files by default in not consistant with the current documentation (http://maven.apache.org/plugins/maven-checkstyle-plugin/checkstyle-mojo.html).
Moreoever, this lead in my case to a regression: I have a checkstyle rule to enforce that every java file should begin by a special comment (/* Copyright... */). Now checkstyle looks at this pattern also for properties files!
Oddly, *.properties files seem to be taken into account only during the "site" phase, but not during the default lifecycle.
                
> Allow src/main/resources to be searched by Checkstyle
> -----------------------------------------------------
>
>                 Key: MCHECKSTYLE-184
>                 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-184
>             Project: Maven 2.x Checkstyle Plugin
>          Issue Type: New Feature
>    Affects Versions: 2.9.1
>            Reporter: Dennis Lundberg
>            Assignee: Dennis Lundberg
>             Fix For: 2.10
>
>
> There is a nice check in Checkstyle that allows you to keep your localized resource bundles in sync.
> <module name="Translation"/>
> http://checkstyle.sourceforge.net/config_misc.html
> In its current state maven-checkstyle-plugin cannot make use of this check, for two reasons:
> # maven-checkstyle-plugin only recognizes {{\*\*/\*.java}} files. This can be re-configured with the <includes> parameter.
> # maven-checkstyle-plugin supports only one source directory, which is configured with the <sourceDirectory> parameter.
> We need to be able to add a resource directory (/src/main/resources by default) that is searched for {{\*\*/\*.properties}} files by default.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira