[
https://issues.apache.org/jira/browse/LUCENE-10195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17434362#comment-17434362
]
Dawid Weiss commented on LUCENE-10195:
--------------------------------------
bq. I'd rather have the local related settings in ~/.gradle/gradle.properties
which takes precedence over the project's gradle.properties
The thing is: these are global. And many of these settings are
project-specific. What works in one project wouldn't work in another. I found
it irritating that something so easily solved in ant (include defaults, then
local user properties from the project) is so difficult in gradle. I know I'm
in no position to suggest anything but I would love to see a way of
bootstraping with more than one project-local gradle*properties... or to have a
way to compute some of the properties dynamically (so that machine settings can
be fined-tuned to).
> Gradle build speed improvement
> ------------------------------
>
> Key: LUCENE-10195
> URL: https://issues.apache.org/jira/browse/LUCENE-10195
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Jerome Prinet
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Increase Gradle build speed with help of Gradle built-in features, mostly
> cache and up-to-date checks
>
--
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
