This covers forking of processes that outlive the Gradle build process itself. Is it possible? Would termination of the build cause the child processes to terminate? How to work around that?
What about terminating the process in a subsequent Gradle build execution? For example:
task start << {
project.procs.fork { }
}
task stop << {
//somehow terminate the process
}
Currently the API only exposes a waitForFinish, how do we term the program? How do we pick up the right process in the subsequent build? Do we do pattern matching? Is there a way to get the PID (PIDs are not exposed through the Java Process API, how do we merge the concepts between *nix and Windows?)
This covers forking of processes that outlive the Gradle build process itself. Is it possible? Would termination of the build cause the child processes to terminate? How to work around that?
What about terminating the process in a subsequent Gradle build execution? For example:
Currently the API only exposes a waitForFinish, how do we term the program? How do we pick up the right process in the subsequent build? Do we do pattern matching? Is there a way to get the PID (PIDs are not exposed through the Java Process API, how do we merge the concepts between *nix and Windows?)