I also wonder how weaving in-place will interact with incremental compilation

Incremental compilation would not be affected, because weaving does not take part in the compilation itself like annotation processors do (i.e. it can’t introduce new APIs that the user could call)

Or incremental

Long-term we could make this a first-class citizen by having a task dedicated to weaving where people can plugin all their bytecode fiddling tools

That would also solve incrementalism nicely

Unfortunately the way the Java plugin is currently set up (with lots of plugins depending on the value

JavaCompile.destinationDir

), doing this yourself is painful, because you have to fix up every plugin that uses this value.

If

JavaCompile

had its own

destinationDir

and nobody directly depended on that, but only on

output.classesDir

, then the

classes

task could do a copy+weave.