Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-32298

JavaDoc console warnings are irgnored

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: warnings-plugin
    • Labels:
      None
    • Environment:
      Debian 3.2.65-1+deb7u2
      Oracle JRE 1.8.0_45-b14
      Jenkins 1.634
      warnings 4.51
      Jenkins gets started by java -jar jenkins.war
    • Similar Issues:

      Description

      Although JavaDoc finds errors and these are displayed in the console for that build, the warnings plugin does not show them in its report.

      There are five successful builds in the history before I triggerd the job again. Below i will paste some output from the console:

      [...]
      [javadoc] Generating Javadoc
      [javadoc] Javadoc execution
      [javadoc] Loading source files for package XXX...
      [javadoc] Constructing Javadoc information...
      [javadoc] Standard Doclet version 1.8.0_45
      [javadoc] Building tree for all the packages and classes...
      [javadoc] /home/XXX/.jenkins/jobs/SDK/workspace/Commons/src/de/XXX/XXX/commons/JBossDatasourceController.java:12: error: package org.jboss.as.cli does not exist
      [javadoc] import org.jboss.as.cli.CommandContext;
      [javadoc]                        ^
      [... more Javadoc errors are displayed ...]
      [javadoc] 9 errors
      BUILD SUCCESSFUL
      Total time: 4 seconds
      [... TASKS plugin output ...]
      [WARNINGS] Parsing warnings in console log with parser Java Compiler (javac)
      [WARNINGS] Parsing warnings in console log with parser JavaDoc Tool
      [WARNINGS] Computing warning deltas based on reference build #57
      [WARNINGS] Ignore new warnings since this is the first valid build
      [WARNINGS] Plug-in Resultat: Erfolgreich - Kein Grenzwert wurde ├╝berschritten
      

      As you can see, there are errors but they are either ignored or not found.

      As a side note, many other plugins like TASKS, CHECKSTYLE and FINDBUGS also print "Ignore new warnings since this is the first valid build" during the post build process, so maybe the root of this problem is not the warnings plugin?

        Attachments

          Activity

          Hide
          drulli Ulli Hafner added a comment -

          Note that the message consists of several lines now. This information is not shown since the parsers scans only a single line.

          Show
          drulli Ulli Hafner added a comment - Note that the message consists of several lines now. This information is not shown since the parsers scans only a single line.
          Hide
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Ulli Hafner
          Path:
          src/test/java/hudson/plugins/warnings/parser/ParserRegistryTest.java
          http://jenkins-ci.org/commit/warnings-plugin/cadfb2a071bf1045b9c74af45b9ea1cf57958e74
          Log:
          JENKINS-32298 Update of testcase due to new parser regexp.

          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Ulli Hafner Path: src/test/java/hudson/plugins/warnings/parser/ParserRegistryTest.java http://jenkins-ci.org/commit/warnings-plugin/cadfb2a071bf1045b9c74af45b9ea1cf57958e74 Log: JENKINS-32298 Update of testcase due to new parser regexp.
          Hide
          bjacobsen Bob Jacobsen added a comment -

          Thanks for looking at this!

          Warnings like this line do come through OK:

          [javadoc] javadoc: warning - Warning: node c7261778, port p unrecognized

          That's from a custom doclet that we use to create UML diagrams. That message (and similar ones) comes through fine.

          Show
          bjacobsen Bob Jacobsen added a comment - Thanks for looking at this! Warnings like this line do come through OK: [javadoc] javadoc: warning - Warning: node c7261778, port p unrecognized That's from a custom doclet that we use to create UML diagrams. That message (and similar ones) comes through fine.
          Hide
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Ulli Hafner
          Path:
          src/main/java/hudson/plugins/warnings/parser/JavaDocParser.java
          src/test/java/hudson/plugins/warnings/parser/JavaDocParserTest.java
          http://jenkins-ci.org/commit/warnings-plugin/81c697a5d0479843c75fed907f94c9bd9bb6c696
          Log:
          JENKINS-32298 Fixed false positives after upgrade to JavaDoc 8.

          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/warnings/parser/JavaDocParser.java src/test/java/hudson/plugins/warnings/parser/JavaDocParserTest.java http://jenkins-ci.org/commit/warnings-plugin/81c697a5d0479843c75fed907f94c9bd9bb6c696 Log: JENKINS-32298 Fixed false positives after upgrade to JavaDoc 8.
          Hide
          bjacobsen Bob Jacobsen added a comment -

          Confirming that this is now fixed in plugin 4.54.

          Thank you!

          Show
          bjacobsen Bob Jacobsen added a comment - Confirming that this is now fixed in plugin 4.54. Thank you!

            People

            • Assignee:
              drulli Ulli Hafner
              Reporter:
              bennyprange Benny Prange
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: