gradle

WorkerDaemonClients are retained across builds, so any object associated with

it must not contain project state since this will be kept around until the worker

expires.

- Introduce a newDecoratedJavaForkOptions which creates a decorated JavaForkOptionsInternal

- Replace calls to the decorated version of the method with non-decorated versions where appropriate

This fixes a problem where, in a composite build, a worker can get a context

classloader set to a classloader from another project, which causes a class

mismatch when we attempt to re-hydrate a legacy runnable class in AdapterWorkAction.

We now ensure that the context classloader for no-isolation workers get set

to the context classloader of the thread that submitted the work.