attempt to fix empty ontology exception
add test using the exact RDF/JSON that is uploaded by javascript

test failed initially for another reason but now passes....
add content assertions for test and cleanup
Fix one test that started to break in Java-8
hack: hide two other bugs by preserving iteration order using
LinkedHashSet
hide another iteration order bug for the simple test using linkedhashset

now going to create breaking versions using a different iteration order
to reliably test the issue
try unsuccessfully to make the trivial case fail with a different
iteration order
note about where the iteration order bug lies
add test that should reliably break in java8 and java7
sort after importsMap is complete for the best results

fix test that already had a note about breaking on different JVMs,
converted it to a general check on the indexes of two ontologies that
have a dependency while leaving it open for the third, other than
checking for existence
migrate setup code back again for realistic test
sort
work on test
fix StackOverflowError caused by copy/replace
Add breaking test for V2

Slightly strange that the equivalent test for V1 worked perfectly

The fact that many abstract test cases are using V1 still may explain
this
add another breaking test
work on tests to make current version tests work

unfortunately now the v1 test is not working anymore
Work on comparator, but break a different test

Breaking test right now is testImportsOrderFourLevelsOutOfOrder
break different tests by changing comparator again

hopefully getting closer to getting a full fix, thanks to a good
testsuite!
break realistic test again, while passing all other tests