We are currently using Warning NG to report java and gcc compiler warnings. For about a month now the scanForIssue tool:  gcc has been grabbing java warnings and reporting it in both the java and cpp section of our report. There are some additional warnings in the cpp section of the report. The warning are "Signal is internal proprietary API and may be removed in a future release" but on different lines of the file.

          [JENKINS-68396] Gcc scans and reports java warnings

          Ulli Hafner added a comment -

          Can you please add the line in plain text that will be parsed by both parsers?

          Ulli Hafner added a comment - Can you please add the line in plain text that will be parsed by both parsers?

          Are you talking about the lines that show up in the console log?

           

          Benjamin Leheup added a comment - Are you talking about the lines that show up in the console log?  

          Benjamin Leheup added a comment - parsedfile.txt

          Ulli Hafner added a comment -

          Yes, that is exactly what I needed. Then someone can pick up this file and create a new unit test for the affected parsers.

          Ulli Hafner added a comment - Yes, that is exactly what I needed. Then someone can pick up this file and create a new unit test for the affected parsers.

          Is there a way to configure the gcc to not report the javac warnings?

          Benjamin Leheup added a comment - Is there a way to configure the gcc to not report the javac warnings?

          Ulli Hafner added a comment -

          No

          Ulli Hafner added a comment - No

          I know its a long shot, is there another scanForIssue tool that would only catch the c warnings or is gcc the only one.

          Benjamin Leheup added a comment - I know its a long shot, is there another scanForIssue tool that would only catch the c warnings or is gcc the only one.

          Until this is fixed, perhaps you can work around the issue by redirecting the gcc warnings to one file and the java warnings to another file, and then scanning those files rather than the console log.

          Kalle Niemitalo added a comment - Until this is fixed, perhaps you can work around the issue by redirecting the gcc warnings to one file and the java warnings to another file, and then scanning those files rather than the console log.

          shamly mhd added a comment -

          Hi, can I start to work on this issue? 

          shamly mhd added a comment - Hi, can I start to work on this issue? 

            Unassigned Unassigned
            bleheup Benjamin Leheup
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: