Dario Djuric created MCHECKSTYLE-330:
----------------------------------------

             Summary: Inconsistent reporting for JavaDoc errors
                 Key: MCHECKSTYLE-330
                 URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-330
             Project: Maven Checkstyle Plugin
          Issue Type: Bug
            Reporter: Dario Djuric


We have started using Checkstyle in our environments and have noticed 
inconsistent reporting for one JavaDoc issue on our work machines and our build 
server (Jenkins).

Specifically, sometimes (but not always), Jenkins reports the following error:

{quote}
SingleLineJavadoc: Javadoc comment at column 87 has parse error. Missed HTML 
close tag 'NN'. Sometimes it means that close tag missed for one of previous 
tags.
{quote}

The above violation is valid and indeed the tag is not closed properly, however 
I am interested to know why this error is not always reported, but only 
occasionally and only on our build server.

This is the Maven configuration:

{code:xml}
<plugin>
    <artifactId>maven-checkstyle-plugin</artifactId>
    <version>2.17</version>
    <dependencies>
        <dependency>
            <groupId>com.puppycrawl.tools</groupId>
            <artifactId>checkstyle</artifactId>
            <version>7.2</version>
        </dependency>
    </dependencies>
    <configuration>
        
<configLocation>https://raw.githubusercontent.com/Altima-Zagreb/Checkstyle/master/checkstyle.xml</configLocation>
        <violationSeverity>warning</violationSeverity>
        <logViolationsToConsole>true</logViolationsToConsole>
        <failOnViolation>true</failOnViolation>
        <failsOnError>true</failsOnError>
        <includeTestSourceDirectory>true</includeTestSourceDirectory>        
    </configuration>
    <executions>
        <execution>
            <id>checkstyle</id>
            <goals>
                <goal>check</goal>
            </goals>
            <phase>verify</phase>
        </execution>
    </executions>
</plugin>
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to