[
https://jira.codehaus.org/browse/MCHECKSTYLE-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=298612#comment-298612
]
Peter Ford commented on MCHECKSTYLE-176:
----------------------------------------
N.B. The difference between this (feature request in the
mvn-checkstyle-plugin) and the 'upstream' feature request
([2836054|http://sourceforge.net/tracker/?func=detail&aid=2836054&group_id=29721&atid=397081])
could be that in the former case, the underlying checkstyle code would not
even _see_ any generated {{.java}} files, because Maven would exclude them.
Arguably, in the latter case, Checkstyle would look inside _every_ {{.java}}
file, and only ignore those program elements with the annotation. So
Checkstyle would still always process rules on parts of the file that can't be
annotated - such as import statements.
(Also, 2836054 is nearly 3 years old.)
> Support for @javax.annotation.Generated
> ---------------------------------------
>
> Key: MCHECKSTYLE-176
> URL: https://jira.codehaus.org/browse/MCHECKSTYLE-176
> Project: Maven 2.x 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
