Simplify the Java compiler scanner tool

Previous attempts to overcomplicate this were counterproductive. The
short of it is that the Java compiler backend can generate additional
class files by way of transforming more complex language constructs into
simpler ones, which occurs AFTER the parsing stage. This means that the
source code parsing approach cannot work at all, since the list of
outputs depends on the compiler internals rather than solely on the
structure of the Java source code.

The source code parsing approach was advised against by a JDK engineer
who suggested alternative approaches.

Unfortunately, this patch "breaks" dry-run builds since dependencies may
not present when building Java source files... which is why this became
overcomplicated in the first place. TypeScript has the same issue, which
would be even more challenging to "solve" in a similar way as I tried to
"solve" the dry run issue for Java.

Task-number: QBS-1069
Change-Id: I8cef2268cd8845eda9f098e90decb81a40b2ab9c
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>

0 files changed, 0 insertions, 0 deletions