Prevent internal buildSrc compiler to spawn a daemon

Help/Discuss
1

Hi,

I’m trying to circumvent the IllegalAccessError when running a Gradle build on jdk-9. When using “” and “daemon=false” it almost builds: https://travis-ci.org/junit-team/junit5/builds/217637646

Now, the internal buildSrc handling spawns a worker daemon, that runs into the module wall…
How do I prevent a daemon to be spawned?

Find my current Gradle/Travis configuration here: https://github.com/junit-team/junit5/compare/travis_jkd9_build

Cheers!

1 Like
2

Update

  • remove “./buildSrc” from code base solves the daemon issue. It doesn’t matter which source language is used within “./buildSrc”, it is always compiled with a new worker daemon – that breaks the build on jdk-9
  • update Groovy from 2.4.7 to 2.4.10 solved groovy.lang.MissingMethodExceptions, like:
    • No signature of method: java.io.File.isFile() is applicable for argument types: () values: []

Now, we run into “real” user-code problem within our code: https://travis-ci.org/junit-team/junit5/builds/218263393

Is there a switch to prevent buildSrc being build by daemon?
Will Gradle 3.5 ship with a Groovy-all version that includes the fix for MissingMethodExceptions?

Cheers,
Christian

1 Like
3

From https://docs.gradle.org/3.5-rc-3/release-notes.html

The version of Groovy bundled with Gradle has been upgraded to 2.4.10 :slight_smile:

Now, only the daemon(s) issue persits: https://github.com/gradle/gradle/issues/1461

Cheers,
Christian

4

JDK_JAVA_OPTIONS did the trick!

Cheers!