[
https://issues.apache.org/jira/browse/LUCENE-9179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024450#comment-17024450
]
Dawid Weiss commented on LUCENE-9179:
-------------------------------------
We don't need a recursive build at all -- it will just generate defaults and
continue to run. I only wanted to run recursively because I hoped the new
machine-specific defaults would be picked up (I don't think they are, not in
full).
> gradle setupLocalDefaultsOnce can screw up on the first run
> -----------------------------------------------------------
>
> Key: LUCENE-9179
> URL: https://issues.apache.org/jira/browse/LUCENE-9179
> Project: Lucene - Core
> Issue Type: Task
> Reporter: Robert Muir
> Priority: Major
>
> To reproduce:
> {noformat}
> rm gradle.properties
> ./gradlew -p lucene test
> {noformat}
> It will fail with a strange error:
> {noformat}
> > Included build in /home/rmuir/workspace/lucene-solr/lucene has name
> > 'lucene' which is the same as a project of the main build.
> {noformat}
> It makes me wonder if we should try to do this recursive build stuff at all
> on the first time, or do it a different way (e.g. alternatives are to fail
> build, or maybe simply invoke ./gradlew ourselves so that it also picks up
> parallelism changes)?
--
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
