If we use compression, reading the Siebel responses gives EOFException.
In debug i see the compressed data is decompressed (i can read the text)
but i think reading in the chunked data fails near/at the last line. Not
using compression fixes this for us.
Yarden specific logic to handle symbols and a list of values in output
comparison.
https://atlassian.intern.yarden.nl/confluence/display/SoftOnt/Yarden+specifieke+Fitnesse+aanpassingen
Revert "Yarden specific logic to handle symbols and a list of values in output"

This reverts commit b7c799474fa194b7b12d6837154067bb4f6b5047.
Revert "If we use compression, reading the Siebel responses gives EOFException."

This reverts commit c41dbd4f14e89e6939f6264c47da58c2f0c0ca96.
Redoing previous change but now hopefully with better eol.
Yarden specific logic to handle symbols and a list of values in output
comparison.
https://atlassian.intern.yarden.nl/confluence/display/SoftOnt/Yarden+specifieke+Fitnesse+aanpassingen
Redoing previous change but now hopefully with better eol.

If we use compression, reading the Siebel responses gives EOFException.
In debug i see the compressed data is decompressed (i can read the text)
but i think reading in the chunked data fails near/at the last line. Not
using compression fixes this for us.
Added test from Yarden source.
Added code to remove characters that interfere with Surefire report
watching. For SLIM this is no issue because an earlier assertion error
is raised in case of a failure that has no invalid characters and
therefore can be processed by Surefire. 
However for FIT, somehow only these last assertions are raised and the
&lt; and &gt; characters cause the TEST-null.xml not to be processed by
Surefire so any failure logged here was not seen.
Merge pull request #3 from ilseh/master

Yarden updates