dweiss commented on PR #14942: URL: https://github.com/apache/lucene/pull/14942#issuecomment-3067663437
> SO with new gradle build infrastrcuture it got much more annoying than before. Previously it was able to track back a change in one of the gradle files and not rebuild everything that was not touched at all. I have the feeling the issue is now that when it compiles one Java file or Gradle file form the build-plugin, the final JAR file changes so the dependency on the build on the plugin causes all task outputs to get invalidated. Very annoying! Yes, could be... I've noticed it too. I don't know the answer though. We have no control over this, unfortunately. We should try to get the build system to a stable state and then it should be a rare event. For now, we'll have to suffer. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
