Hi Mike, Thanks, Mike. So I removed gradle.properties (I never edited anything > in there), and re-run, and I can see that I now have >
This file is generated and contains some defaults optimized for a local machine. Yes, it may change from time to time and these changes will not be picked up automatically. > which seems as if it ought to fix, but I got the same error -- OH -- > but not the second time??! wacky, but (crossing fingers) I hope it will stay fixed now > Here's why. The first time you run gradle after you remove the properties file, the build scripts see the file is not there and regenerate the defaults. However, the gradle instance doesn't automatically pick up the just-generated defaults (it can't, they are JVM-settings) so any subsequent task may fail as if that file wasn't present at all. A subsequent run will pick up the new settings from the gradle.properties file and that's why it worked for you. Perhaps it should be better explained here - if you can find a wording that works, please modify it: https://github.com/apache/lucene/blob/main/help/localSettings.txt In theory we could interrupt (stop) gradle execution if gradle.properties hasn't been generated yet but in practice this would cause more confusion than help. I don't think there is a clean way around it. Dawid
