Adam

(replying with my official JB hat since this is more about the future work rather than in my of-the-clock Dokkatoo work) > To confirm, does that mean the updated Gradle...

One of the tests is failing on TeamCity https://teamcity.jetbrains.com/buildConfiguration/KotlinTools_KotlinxAtomicfu_SandboxBuildLinuxKotlinMaster/4611908?expandBuildDeploymentsSection=false&hideTestsFromDependencies=false&hideProblemsFromDependencies=false&expandBuildProblemsSection=true&expandBuildChangesSection=true ``` > Task :buildSrc:generateExternalPluginSpecBuilders FAILED Watching 14 directories to track changes Watching 14 directories to track changes Resource missing. [HTTP GET:...

> @adam-enko, CI say we can not get rid of: > > ``` > // NOTE: This is a temporary WA, see KT-61313. > tasks.withType().configureEach sign@{ > ``` D'oh! Oh...

One potential benefit of process isolation is that it would allow for [class data sharing](https://docs.oracle.com/en/java/javase/11/vm/class-data-sharing.html#GUID-EC975B2E-B4AB-45B4-B91F-51C3A264D0CE). With a multimodule project, Dokka Generator has to run multiple times with the same classpath....

I think it's probably best to just close this PR. It's not entirely necessary to use test-fixtures, and if they would help, then it would make sense to start again...

EDIT: I made a mistake, the information below is incorrect. --- ~I tried to enable caching by specifying `outputs.cacheIf { true }`~ ```kotlin tasks.npmInstall { outputs.cacheIf { true } }...

> I don't think this does what you think it does. You're right! It wasn't caching as I expected, I misunderstood what was going on.

Hi 👋 I've add an example test of the behaviour I'd like to see in https://github.com/node-gradle/gradle-node-plugin/pull/301 Currently I see warning messages from Gradle that explain why `npmInstall` can't be cached:...