[
https://jira.codehaus.org/browse/MCHECKSTYLE-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=351661#comment-351661
]
Robert Scholte commented on MCHECKSTYLE-176:
--------------------------------------------
Up until now the maven-checkstyle-plugin has no reason to pre-process files. It
just collects all files on source and resource directories, sometimes with
additional includes/excludes, and feeds them to CheckStyle. Adding this to the
plugin will cost extra time, since it has to process every file (which will be
done by Checkstyle for a second time if it was not marked as generated).
The maven-way is to have a folder like
{{target/generates-sources/custom-plugin}} for generated sources. Easy to
recognize and for that reason easy to exclude without reading the files.
> Support for @javax.annotation.Generated
> ---------------------------------------
>
> Key: MCHECKSTYLE-176
> URL: https://jira.codehaus.org/browse/MCHECKSTYLE-176
> Project: Maven Checkstyle Plugin
> Issue Type: New Feature
> Reporter: Peter Ford
> Priority: Minor
>
> Would you be willing to consider whether any support can be added for
> excluding code that is annotated with {{javax.annotation.Generated}}?
> For example, if a {{.java}} file contains a public class that is annotated
> {{@Generated}}, perhaps the whole file would be excluded from checks - if a
> suitable parameter was set in the POM.
> Thanks!
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
