From 3f9995f1dbfab47fc5012f9b5db3f3b39315214a Mon Sep 17 00:00:00 2001
From: Andrew Gvozdev Use the Error Parsers tab on Use the Error Parsers Tab on Error Parsers scan build output looking for potential error or warning messages.
+ They create Problem Markers which help to visualize problems for users.
+ Most of Error Parsers scan build output line by line and check if the line match a certain pattern.
+ This preference page lets define those patterns.
+Error Parser Options
-
- Build preference panel to define global error parsing options.
+ Build preference panel to define global error parsing options.
+
-
+
+
+
+
+
+ Field
+ Description
+
+
+ Severity
+ Defines severity of problem marker to be generated. The choice is one of following:
+
+
+
Error
+
Warning
+
Info
+
Ignore - use this option
+ to suppress generating a marker.
+
+
+ Pattern
+ Java regular expression pattern. This pattern should define groups in parentheses for using
+ in File, Line, and Description fields.
+
+
The pattern is assumed to start from the beginning of line and end at the end,
+ so it is unnecessary to specify starting "^" or ending "$" in the pattern.
+
+
+ File
+ Define a file which will be associated with the problem marker.
+
+
This is a replacement pattern. Use $ notation
+ to refer to one of the the groups defined in Pattern,
+ i.e. $1, $2,$3 etc.
+
+
+ Line
+ Define a line in the file which will be associated with the problem marker.
+
+
This is a replacement pattern like for File field.
+
+
+ Description
+ Define a description which will be assigned to the problem marker.
+
+
This is a replacement pattern like for File field.
+
+
+
+Consume
+ This field defines if the pattern stops processing of output line (consumes it).
+ By default it does (field is empty).
+ Use No if the same line needs to be processed by several patterns.
+
+
-
Error Parsers tab
+
Project properties, Error Parsers tab
Console View
Problems View
Console View
Problems View
+
Make Targets View
Error Parsers tab
Error Parser Options