Build Failure Analyzer sometimes doesn't show error string

[mmitche]

Occasionally even if the BFA detects an error properly, the error string (like compile error) is not indicated even though the replacement (${1,1} for instance) is valid.

I am suspicious that this is caused by multiple indication failure modes, since the first index for the replacement is the "indication number" in the help. That might mean that if you match the 3rd indication, you'd need ${3,1}. But not sure. Will need to experiment.

[mmitche]

So, it turns out that the messages were just configured a bit wrong for the compile errors. The plugin will replace a format descriptor ${1,1} with captured regex. The format descriptor is Indication Number, Capture Group. As it turns out, I misinterpreted what indication number meant. For compile errors, we have multiple indicators corresponding to multiple types of compilers. However, the first number actually means the indicator index, not the "first indication from the log". This is a little odd. but it means that we simply concatenate all of the potential captured strings together:

${1,1}${1,2}$[1,3}

and you'll see the compile error where you expect it.

I am fixing the indications now.