Looking at run 80 workspace, I see Java version 1.8.0 build 102 (I think - this is from memory, and I can't seem to get to the workspace at the moment). I think this might be an Oracle Java.
I ran the test with Oracle Java 8 build 112, on Windows, and got a different slight miscompare - the end of the file had a \r\n in one, not the other. I've (so far) been unable to reproduce having the xml serialization produce the <xyz></xyz> style of empty tags, in my local setup. So, I'm in favor of changing the compare to use xmlunit. The core is using this already (in the project uimaj-json). -Marshall On 11/7/2016 9:33 AM, Richard Eckart de Castilho wrote: > Hi Marshall, > > thanks for identifying this! > > Given that it works with Java != 8, I'd say there was a change in defaults > in the Java 8 XML implementation - or something in the UIMA descriptor > serialization > code changed. > > An alternative to tracking this down could be to use XMLUnit instead of > string comparison. > > Cheers, > > -- Richard > >> On 07.11.2016, at 15:25, Marshall Schor <[email protected]> wrote: >> >> The problem is one test which miscompares the expected and actuals. The >> difference is the empty "description" tags are expected to be written: >> >> <description/> >> >> but the descriptor was written using the long form of empty tags: >> >> <description></description> >> >> Any idea what causes this discrepancy? >> >> -Marshall >
