Leverage gradle daemon in integration tests

[glefloch]

This branch removes gradle daemon deactivation.

Gradle CI jobs normally takes around 40min on linux and 1h on windows.
On my fork with the daemon, it tooks 20min on linux and 38min on windows without any failures.

cc @ebullient

[famod]

Are we sure this is not introducing any side-effects or "caching anomalies"? Maybe an opt out (or opt in) makes sense?

[ebullient]

Are we sure this is not introducing any side-effects or "caching anomalies"? Maybe an opt out (or opt in) makes sense?

Gradle always uses a daemon, even if you "disable" it. When we run our builds by turning off the daemon, we just extend the build time as it starts and stops an entire daemon process.
Also.. gradle is used within our maven targets.. so the maven dependency order will influence what gradle sees / doesn't see.

[famod]

I guess what I was trying to ask is: Are we sure that running test B with the same daemon as test A is always providing the necessary test isolation?
But what do I know, feel free to ignore me. 😉