Join GitHub today
Improve Javac error parsing #557
This is an improvement over the status quo of forked Javac error parsing,
"Normal" Java error messages look like:
However, under certain circumstances javac errors are reported as:
Current parsing assumes existence of
Ultimately a better way of handling forking probably is to define our own small commandline app, like forked tests are done.
Looks good, but a little bit complicated. Thinking: does this approach complement with the complete fix? If it doesn't, maybe we should invest some time in implementing forked java compilation the same way it's done with forked tests (I have no idea how much this would cost, that's why I'm asking).
If I can unblock the customer I am working with, I'd like to get this in soon.