Am 21.11.2017 um 08:28 schrieb Paul King:
The "double" build is because of indy vs non-indy (one wipes out the
other) because of some assumptions that keep other parts of the build
simple. Could no doubt be streamlined given some TLC.
Last I checked there were different performance characteristics between
indy/non-indy. We haven't gotten around to working out the best path
forward yet that will give us one set of jars without losing performance
in some scenarios. Again, just needs some time dedicated to it.
I don't see the old callsite caching still working properly in a Java9
world, so it is time to cut loose
bye Jochen
