This is more complex than I thought a it involves default output paths from source sets and is related to our hacks that build modular classpath.
I'll file an issue and turn off the linter for now so that builds pass. Once I figure out how to fix it, I'll re-enable. D. On Mon, Jul 7, 2025 at 3:59 PM Dawid Weiss <[email protected]> wrote: > > I'll take a look. Better fix these than disable the linter. > > On Mon, Jul 7, 2025 at 1:52 PM Robert Muir <[email protected]> wrote: > >> Hmm I think we still have an issue with "path" lint check: >> >> > Task :lucene:demo:compileTestJava FAILED >> warning: [path] bad path element >> >> "/home/jenkins/workspace/Lucene-main-Linux/lucene/demo/build/resources/main": >> no such file or directory >> error: warnings found and -Werror specified >> 1 error >> 1 warning >> >> Not sure what this is all about: maybe we need an exists() check >> somewhere before adding stuff to a classpath? >> >> On Mon, Jul 7, 2025 at 7:43 AM Policeman Jenkins Server >> <[email protected]> wrote: >> > >> > Build: https://jenkins.thetaphi.de/job/Lucene-main-Linux/56758/ >> > Java: 64bit/hotspot/jdk-25-ea+27 -XX:+UseCompressedOops -XX:+UseSerialGC >> > >> > All tests passed >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [email protected] >> > For additional commands, e-mail: [email protected] >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >>
