ml-gradle doesn't work with Java 11 and the Gradle daemon running

[dmcassel]

Has ml-gradle been tested with Java 11 and Gradle 5? Those are the current versions. I tried using those versions with an existing project, but my modules don't get deployed. Wondering whether anyone else has used ml-gradle successfully under new versions.

[rjrudin]

It has not, and there's an issue with ml-app-deployer regarding this - marklogic/ml-app-deployer#313

If you have a chance, can you see if the same problem exists with Gradle 5 + Java 9 and Java 10, and add results to that ml-app-deployer ticket?

The short-term fix is to not run Gradle in daemon mode, but that's of course not a great fix.

[rjrudin]

Started looking into this - it's not specific to Gradle 5. Java 9 and 10 seem to not matter - seems like the common upgrade path is from Java 8 to 11. So I'm going to focus on supporting Java 11.

@dmcassel One short term hack is to set mlConfigPath and mlModulePaths to absolute paths - e.g. mlConfigPath=/Users/janedoe/project/src/main/ml-config.

[rjrudin]

@dmcassel I have fixes for this in ml-app-deployer with a tiny but critical tweak in ml-gradle - will try to get 3.12.0 out soon to address Java 11 support. Still have the short term hack of setting mlConfigPaths, mlModulePaths, and mlSchemasPath to absolute paths.