[
https://issues.apache.org/jira/browse/LUCENE-9232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17039316#comment-17039316
]
Dawid Weiss commented on LUCENE-9232:
-------------------------------------
I didn't find a way to tell gradle to shut down the "current" daemon gracefully
(even if there seems to be internal API to do so there is no way to access it).
I attach a dumb patch that just passes "--no-daemon" if local gradle.properties
isn't available. Not too elegant but works for me.
I can't say what Eclipse does but IntelliJ uses Gradle's tooling APIs (so yes,
it forks its own internal daemon too). Memory consumption doesn't seem to be an
issue for folks behind gradle (there are discussions on the forum about it).
> 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
> Attachments: LUCENE-9232.patch
>
>
> 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
