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

Warnings not detected when file path does not appear after [WARNING]

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved (View Workflow)
    • Major
    • Resolution: Fixed
    • warnings-plugin
    • None
    • ubuntu, java 1.7.0_02, tomcat7, jenkins 1.447, warnings plugin v3.26, maven-compiler-plugin v2.3.2

    Description

      When compiling a Java project using the javac compiler, most of the warnings in my console log appear as follows:

      [WARNING]     BasicTableInfo
      /absolute/path/to/source/File.java:[143,66] [unchecked] unchecked conversion
      

      and are thus not picked up by the warnings plugin.

      When there is no additional token before the source file path, such as in the following warning:

      [WARNING] /absolute/path/to/source/File.java:[181,69] [unchecked] unchecked cast
      

      then the warning is correctly picked up by the warnings plugin.

      Btw: Coloring in the console log has the same "bug": when the path appears as the first token (after [WARNING]), then the path and the next token (warning category) are highlighted in dark-yellow. When there is an additional token before the path, only that additional token is highlighted in dark-yellow (not the path and subsequent tokens).

      Attachments

        Activity

          People

            drulli Ulli Hafner
            stefanthurnherr Stefan Thurnherr
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: