[ https://issues.apache.org/jira/browse/LUCENE-9179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024395#comment-17024395 ]
Robert Muir commented on LUCENE-9179: ------------------------------------- I know [~mikemccand] hit this trying to use gradle in luceneutils (with a clean checkout like a CI tool might do). As a workaround i suggested he run {{./gradlew help}} first so that it generates the properties file, then run again. > 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