uschindler commented on PR #14942: URL: https://github.com/apache/lucene/pull/14942#issuecomment-3067002518
> I only added the configuration example and suppressions on everything so that you can see where to put the stick in to change it. Thanks for following up. All fine! I just said, if you want to show a failure for somebody just watching the issue with webrowser, it is better to let the build system fail build and all is open on table :-) One annoying thing: I spend several minutes here all the time when I changed a single line of code in the plugin code. Because when the build plugin changes the WHOLE downstream build needs to be repeated. This is very annoying. Why the hell does it need to compile core classes again when just the build plugin changes? I only changed one piece not affecting compilation. 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! -- 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