[
https://issues.apache.org/jira/browse/LUCENE-9179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024479#comment-17024479
]
ASF subversion and git services commented on LUCENE-9179:
---------------------------------------------------------
Commit b420ef8f77209690dcd47e45700a952409ccac62 in lucene-solr's branch
refs/heads/master from Dawid Weiss
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=b420ef8 ]
LUCENE-9179: don't invoke the same build recursively upon first run, just
continue. Seems like gradle bug but let's not cry about it - it just happens
once and CI defaults can be passed independently on command-line.
> 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
> Assignee: Dawid Weiss
> 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
