Compiler warnings from console miscalculated if console annotation is used

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major
    • Component/s: warnings-plugin
    • None
    • Environment:
      Jenkins 1.409.2, Warnings plugin 3.22, Timestamper 1.2.2, Eclipse compiler parser

      When one has console annotations enabled (e.g. via the Timestamper plugin), the warnings count is (sometimes) miscalculated. And worse: the warnings change from build to build without code changes.

      Warnings look the e.g. like this:

      DataProviderHelper.java:80, Eclipse Java Compiler, Priority: Normal

      [8mha:AAAAdB+LCAAAAAAAAABb85aBtbiIQSOjNKU4P0+vIKc0PTOvWK8kMze1uCQxtyC1SC8ExvbLL0llgABGJgZGLwaB3MycnMzi4My85FTXgvzkjIoiBimoScn5ecX5Oal6zhAaVS9DRQGQNu5k0LsPAPYXhGGBAAAA[0mPropertyModel is a raw type. References to generic type PropertyModel should be parameterized

      DataProviderHelper.java:80, Eclipse Java Compiler, Priority: Normal

      [8mha:AAAAdB+LCAAAAAAAAABb85aBtbiIQSOjNKU4P0+vIKc0PTOvWK8kMze1uCQxtyC1SC8ExvbLL0llgABGJgZGLwaB3MycnMzi4My85FTXgvzkjIoiBimoScn5ecX5Oal6zhAaVS9DRQGQNu5k0HsAAMs64teBAAAA[0mPropertyModel is a raw type. References to generic type PropertyModel should be parameterized

      The plugin doesn't seem to recognize the 2 warnings as duplicate and therefore counts them as 2 warnings

            Assignee:
            Ulli Hafner
            Reporter:
            kutzi
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: