You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Ernst de Haan (JIRA)" <ji...@codehaus.org> on 2011/11/10 09:10:51 UTC

[jira] Commented: (MCHECKSTYLE-166) Dro @requiresDependencyResolution test

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

Ernst de Haan commented on MCHECKSTYLE-166:
-------------------------------------------

In the title, _Dro_ should be _Drop_.

> Dro @requiresDependencyResolution test
> --------------------------------------
>
>                 Key: MCHECKSTYLE-166
>                 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-166
>             Project: Maven 2.x Checkstyle Plugin
>          Issue Type: Bug
>    Affects Versions: 2.8
>         Environment: N/A
>            Reporter: Ernst de Haan
>            Priority: Minor
>
> Currently, the [{{CheckstyleViolationCheckMojo}}|http://svn.apache.org/viewvc/maven/plugins/tags/maven-checkstyle-plugin-2.8/src/main/java/org/apache/maven/plugin/checkstyle/CheckstyleViolationCheckMojo.java?revision=1188083&view=markup] class declares:{code}@requiresDependencyResolution test{code}However, that should not be necessary. Checkstyle works on source files, not on bytecode.
> If this declaration would be removed, then this Checkstyle plugin should still work perfectly fine (I would expect without any further code changes).
> The advantage would be that in our Continuous Integration pipeline I can skip the _compile_ stage and immediately trigger the _checkstyle_ stage. That would save us multiple minutes on the feedback roundtrip.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira