On 17 March 2014 at 8:19:19 pm, Szczepan Faber (szczepan.fa...@gradleware.com) wrote:
So I've changed the names of the processes a while ago. I'm wondering if it would useful to create empty classes like GradleTestExecutor extends GradleWorkerMain and GradleCompilerDaemon extends GradleWorkerMain, plug them in, then enjoy better output from jps -m / ps (useful when debugging process issues). +1 Cheers! On Thu, Feb 20, 2014 at 9:18 PM, Adam Murdoch <adam.murd...@gradleware.com> wrote: On 21 Feb 2014, at 6:24 am, Szczepan Faber <szczepan.fa...@gradleware.com> wrote: Hey guys, Is there a specific reason why all our worker processes (compiler, test executor, findbugs, etc.) are named the same way "Gradle Worker x"? It seems better if we call them "Gradle Compiler Daemon x", "Gradle Test Executor x", etc. There’s no reason, other than we haven’t given the WorkerProcessBuilder client a way to give a display name yet. Feel free to add it. -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com -- Szczepan Faber Principal engineer@gradle; Founder@mockito
