tree 2d3b3a20b1fc1c2b0bceeaa694e8e2d6f4aee4ee
parent 374fa7f0da278d46a4c3adb587f4b43089f5d7db
author Mis012 <Michael.Srba@seznam.cz> 1708024916 +0100
committer Jussi Pakkanen <jpakkane@gmail.com> 1717973333 +0300

java: use single javac invocation per jar

Instead of invoking javac for every .java file, pass all of the sources
for a jar target to a single javac invocation. This massively improves
first compilation time and doesn't meaningfully affect incremental builds
(it can even be faster in some cases).

The old approach also had issues where files would not always get recompiled
even though they should, necessitating a clean rebuild in order to see changes
reflected in the build output.

Multiple invocations seem to only make sense if:
- issues with files not getting flagged for rebuild are investigated and fixed
- something like the javaserver buildtool from openjdk sources is used
instead of directly spawning javac processes
- the amount of java files per jar is so large that it is faster to compile
several files one by one than to compile all the files at once (batching may
still make sense to get a reasonable balance)