[
https://issues.apache.org/jira/browse/LUCENE-9232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17039016#comment-17039016
]
Dawid Weiss commented on LUCENE-9232:
-------------------------------------
Not trying to justify anything but Gradle tells you when it can't reuse the
same daemon (and for whatever reason). This isn't a feature anymore – it's the
default. Disabling the daemon will still fork a new one on each invocation.
I s4ill think having it on is a saner default (with a reasonably short timeout)
than launching a new daemon over and over again – if you don't like it you can
disable it locally but I'm not convinced this should be the default for
everyone around.
> disable gradle daemon by default
> --------------------------------
>
> Key: LUCENE-9232
> URL: https://issues.apache.org/jira/browse/LUCENE-9232
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Robert Muir
> ` Priority: Major
>
> We should disable the gradle daemon by default: the user can opt-in by
> changing the properties file.
> If you forget to do this, you end out with leaked JVMs everywhere. It won't
> just leak one daemon, it will leak multiple ones.
> I ran {{ps}} on my laptop, surprised at 13:00 to find 2 leaked gradle jvms
> when I hadn't used the thing since 07:00.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
