Hi,
Some times ago, (before we had to shutdown the demos for a while for a security reason, it's unrelated but) we were (also) forced to stop and quickly
restart the demos because of the Gradle daemons logging taking all the place; though we don't use Gradle daemons in demos. Weird isn't ?
The reason is that by default org.gradle.logging.level=lifecycle is verbose. Anyway, all org.gradle.logging.level are verbose. I mean they also
duplicate OFBiz information, have a look into your own Gradle daemon dir!
And that even if you don't use daemons, as we do for demos. Because Gradle
always uses at least 1 daemon to run.
So I was looking for a solution to not uselessly clutter the VM disk demos and stumbled upon Gradle logging hygiene · Issue #2688 · gradle/gradle
(github.com) <https://github.com/gradle/gradle/issues/2688>
I have created OFBIZ-12085 to use the same solution than Evgeny Naumenko at
https://discuss.gradle.org/t/gradle-daemon-produces-a-lot-of-logs/9905
I'll commit in a week if nobody is against or has a better solution
Jacques
