Some unit tests fail on Windows due to cr/lf encoding
Description
When building jbehave-core on windows, 2 unit tests fail because the files are compared with cr/lf line endings (this may depend on the git default setting for text files) but the actual test results contain lf line endings only (since the text is never written or read).
I ignored that until now with skipTests=true, I assume nobody else uses Windows to build jbehave, if you want, I can fix the tests.
When building jbehave-core on windows, 2 unit tests fail because the files are compared with cr/lf line endings (this may depend on the git default setting for text files) but the actual test results contain lf line endings only (since the text is never written or read).
I ignored that until now with skipTests=true, I assume nobody else uses Windows to build jbehave, if you want, I can fix the tests.