I opened https://github.com/apache/lucene/issues/13695 to try to get to the bottom of this.
Mike McCandless http://blog.mikemccandless.com On Tue, Aug 27, 2024 at 4:29 PM Michael McCandless < luc...@mikemccandless.com> wrote: > Hi Team, > > When I run "gradle check" on main, sometimes I get seemingly false > positive warnings about dozens of unferenced license files, like this: > > WARNING: there were unreferenced files under license folder: > - /s1/l/trunk/lucene/licenses/antlr4-runtime-LICENSE-BSD.txt > - /s1/l/trunk/lucene/licenses/antlr4-runtime-NOTICE.txt > - /s1/l/trunk/lucene/licenses/asm-LICENSE-BSD_LIKE.txt > - /s1/l/trunk/lucene/licenses/asm-NOTICE.txt > - /s1/l/trunk/lucene/licenses/asm-commons-LICENSE-BSD_LIKE.txt > - /s1/l/trunk/lucene/licenses/asm-commons-NOTICE.txt > - /s1/l/trunk/lucene/licenses/assertj-core-LICENSE-ASL.txt > - /s1/l/trunk/lucene/licenses/assertj-core-NOTICE.txt > - /s1/l/trunk/lucene/licenses/commons-codec-LICENSE-ASL.txt > - /s1/l/trunk/lucene/licenses/commons-codec-NOTICE.txt > ... > > If I then do a "./gradlew clean" and again "./gradlew check" the warnings > seem to go away, but then if I immediately run "./gradlew check" again > (after clean then check), the warnings return. > > Does anyone know why this happens? Can we stop the false positives? God > forbid I someday actually introduce a true positive warning, I would never > notice :) > > Mike McCandless > > http://blog.mikemccandless.com >
