[m-rev.] for post-commit review: java bootcheck

[Zoltan Somogyi]

I just got a new laptop, and I am starting to use it for work. Unlike the old one,
this one has current Java and C# compilers, so I tried a Java bootcheck.
After I fixed an issue specific to me (I have ALWAYS_MAKE_TAGS_FILE set),
the bootcheck finished, though with 72 unexpected test failures, as listed in
the attached bootcheck output file. Is this typical?

The attached diff contains diffs to three files (committed separately), one of which
handles ALWAYS_MAKE_TAGS_FILE, while the other two should make a start
on fixing some of those 72 test failures. I could use reviews for these.

Tomorrow I will try C#.

Zoltan.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: DIFF.java1
Type: application/octet-stream
Size: 2132 bytes
Desc: not available
URL: <http://lists.mercurylang.org/archives/reviews/attachments/20190618/ec7da6c2/attachment-0001.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Out.jun17a.gz
Type: application/gzip
Size: 82268 bytes
Desc: not available
URL: <http://lists.mercurylang.org/archives/reviews/attachments/20190618/ec7da6c2/attachment-0001.gz>