Description Harald 2010-10-15 13:06:12 EDT

Build Identifier: 6.0.0.201004122116

I've seen, that following call in the blue print is wrong (I think):
  int status = stepBuilder.build( consoleOutStream, epmOutputStream, 
                   new SubProgressMonitor( monitor, 1, subProgressMonitor.PREPEND_MAIN_LABEL_TO_SUBTASK));
 
epmOutputStream is the stream of the ErrorParserManager an consoleOutStream the stream of the console. 
 
With our toolchain we've the problem, that for the compile errors no problem markers are generated, when the command "Build selected File(s)" is executed. I think they are not on the err stream and thus are not scanned by the ErrorParserManager. 

I've patched in my CDT the call to 
  int status = stepBuilder.build( epmOutputStream, epmOutputStream, 
                   new SubProgressMonitor(monitor, 1, SubProgressMonitor.PREPEND_MAIN_LABEL_TO_SUBTASK));
and the problem markers are generated.


Reproducible: Always

Steps to Reproduce:
MBS with internal builder
1. Select a c file with errors
2. Run command "Build selected File(s)"
3. Now Problem marker is generated