Like maven have mvnDebug vs mvn out of the box.
Does gradle? Rather than set/unset the OPTS everytime ?
> -Dorg.gradle.daemon.debug=true on https://docs.gradle.org/current/userguide/command_line_interface.html?&_ga=2.31264959.1270406471.1517316816-1028277259.1515509640#sec:command_line_debugging does not seem to be a vlid thing to pass on commandline > > PS C:\Users\hoaphan\TestTask> gradle -Dorg.gradle.daemon.debug=true myTask > > FAILURE: Build failed with an exception. > > * What went wrong: > Task '.gradle.daemon.debug=true' not found in root project 'TestTask'. > > * Try: > Run gradle tasks to get a list of available tasks. Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights. > > * Get more help at https://help.gradle.org
I think the doc is wrong, also it does not make much sens to have -D…=true while default is already false. It should be a flag, if it does exist.