ClearCase InteractiveProcess ignores error stream

FishEyes ClearCase support uses an interactive ClearCase client for a number of operations. This is basically a long-running cleartool shell that is kept around to limit the overhead of executing cleartool commands. However, our CleartoolInteractiveProcess ignores the error stream completely (it is not read), which causes FishEye to miss any error messages describing error conditions.

In some cases, Cleartool returns a status 0 (no error) but writes an error to the errorstream. One such example is when you run

lsactivity -fmt "%[versions]Cp" activity:adding_a_test_file@/fe_pvob

while you're not in a view directory. In this case cleartool -status will output the following

[atlassian@clearcase views]$ ct -status
cleartool 1> lsactivity -fmt "%[versions]Cp" activity:adding_a_test_file@/fe_pvob
cleartool: Error: No view context available
Command 1 returned status 0
cleartool 2>