[
https://issues.apache.org/jira/browse/MCHECKSTYLE-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16859274#comment-16859274
]
Hudson commented on MCHECKSTYLE-54:
-----------------------------------
Build succeeded in Jenkins: Maven TLP » maven-checkstyle-plugin »
MCHECKSTYLE-54 #6
See
https://builds.apache.org/job/maven-box/job/maven-checkstyle-plugin/job/MCHECKSTYLE-54/6/
> checkstyle:check does not see provided scope dependencies
> ---------------------------------------------------------
>
> Key: MCHECKSTYLE-54
> URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-54
> Project: Maven Checkstyle Plugin
> Issue Type: Bug
> Affects Versions: 2.1
> Reporter: Stephen Duncan Jr
> Assignee: Dennis Lundberg
> Priority: Critical
> Fix For: 2.2
>
> Attachments: MCHECKSTYLE-54.zip, requires-dep-resolution.patch
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Running checkstyle:check against a project that uses Exceptions from
> dependencies that are provided scope causes checktyle errors such as the
> following:
> <file
> name="/share/duncans/workspace/eclipse/cdcie-webapp-feedreader/src/main/java/mil/jfcom/cie/portal/feedreader/converter/ConverterImpl.java">
> <error line="0" severity="error" message="Got an exception -
> java.lang.RuntimeException: Unable to get class information for
> ValidationException." source="com.puppyc
> rawl.tools.checkstyle.TreeWalker"/>
> These errors go away when the scope is changed to compile. This does not
> happen for checkstyle:checkstyle; the report correct indicates no checkstyle
> errors. This is preventing us from using the checkstyle plugin to enforce
> checkstyle rules.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
