maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Bentmann (JIRA)" <>
Subject [jira] Commented: (MCHECKSTYLE-54) checkstyle:check does not see provided scope dependencies
Date Sun, 03 Feb 2008 11:42:58 GMT


Benjamin Bentmann commented on MCHECKSTYLE-54:

bq. I have committed a fix for this in r617973.
I was a few minutes too late... anyway, take it as as "worked for me" feedback then.

By the way, I wonder whether @requiresDependencyResolution is really required for the CheckstyleViolationCheckMojo.
It does not invoke Checkstyle directly but forks the CheckstyleReport mojo which in turn gets
the dependencies via its on annotation.

> checkstyle:check does not see provided scope dependencies
> ---------------------------------------------------------
>                 Key: MCHECKSTYLE-54
>                 URL:
>             Project: Maven 2.x Checkstyle Plugin
>          Issue Type: Bug
>    Affects Versions: 2.1
>            Reporter: Stephen Duncan Jr
>            Assignee: Dennis Lundberg
>            Priority: Critical
>             Fix For: 2.2
>         Attachments:, requires-dep-resolution.patch
> 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/">
> <error line="0" severity="error" message="Got an exception - java.lang.RuntimeException:
Unable to get class information for ValidationException." source="com.puppyc
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message