[ 
https://issues.apache.org/jira/browse/MCHECKSTYLE-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15699824#comment-15699824
 ] 

NoƩmi Balassa commented on MCHECKSTYLE-321:
-------------------------------------------

I had the same desire and made it work like this:
{code:xml}
<plugins>
    <plugin>
        <artifactId>maven-checkstyle-plugin</artifactId>
        ...
        <configuration>
            <sourceDirectories>${project.basedir}</sourceDirectories>
            <testSourceDirectories/><!-- This became pointless. -->
        </configuration>
        ...
    </plugin>
</plugins>
{code}
Also:
{code:xml}
<properties>
    <checkstyle.includes>*.xml,src/**/*.java,etc.</checkstyle.includes>
    <checkstyle.resourceIncludes/>
</properties>
{code}
This way there is no differentiation between sources and resources, but that 
can be done in the configuration based on file extensions.

> Be able to check root files
> ---------------------------
>
>                 Key: MCHECKSTYLE-321
>                 URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-321
>             Project: Maven Checkstyle Plugin
>          Issue Type: Improvement
>          Components: checkstyle:check
>    Affects Versions: 2.17
>            Reporter: Vincent Zurczak
>            Priority: Trivial
>
> Today, the Maven Checkstyle plug-in allows to verify files within the Maven 
> directories: sources, test sources, resources and test resources.
> In addition to this, I would personnaly like to verify my *pom.xml* file.
> I have tried many things but I did not succeed in validating my POM files 
> with Checkstyle. And looking at the code, I think I saw why.
> The reason for such a verification is that this file also contains license 
> headers that I would like to keep verified. And I am pretty sure there would 
> be other rules I would like to check (such as indentation, etc).
> If we consider other project kinds, such as Eclipse plug-ins, one may want to 
> verify *plugin.xml* and *feature.xml* files. So, it would be nice to be able 
> to specify *otherIncludes* in the plug-in's configuration. This new parameter 
> would contain a list of files to verify, when they exist.
> If the idea is accepted, I am ready to contribute a patch for this feature.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to