I don't think they should - this is the reason we try to separate them: https://github.com/apache/lucene/blob/main/gradle/ide/intellij-idea.gradle#L32-L33
On Tue, Aug 10, 2021 at 9:53 PM Michael Sokolov <[email protected]> wrote: > > I can no longer reproduce. I wonder if it's possible that IntelliJ had > written something into the build directory that was incompatible with > the JDK I was attempting to use on the command line ...? I have been > switching back and forth between them, and I don't know if they would > use the same output folders? > > On Sun, Aug 8, 2021 at 3:51 AM Dawid Weiss <[email protected]> wrote: > > > > If you can reproduce it locally somehow then it'd be interested in > > looking at it. What I'd probably need is a dump log > > > > ./gradlew ... --debug 1>log.log 2>&1 > > > > so that I can see what it's doing, exactly. > > > > Your environment variables shouldn't really matter... it's weird that > > the path workaround worked. > > > > D. > > > > On Sat, Aug 7, 2021 at 10:54 PM Michael Sokolov <[email protected]> wrote: > > > > > > Thanks Dawid - I did try those things and they didn't really shed any > > > light. However later I have set my path in the enclosing shell > > > (PATH=$JDK11:$PATH) and all seems to be well!? Also I found that > > > IntelliJ was helpful. So I am out of the woods now and sadly don't > > > have any clear idea where I was when I was lost. I'll report back if I > > > can reproduce and have any suggestions or more questions though. > > > > > > On Sat, Aug 7, 2021 at 4:29 PM Dawid Weiss <[email protected]> wrote: > > > > > > > > Hi Mike. The first thing I'd do is what gradle suggests - run with > > > > --stacktrace or --info. This should show more insightful information > > > > about what failed. We also assemble the full command-line for javac > > > > and write it under the project's tmp folder (somewhere, can't remember > > > > the exact path) - you can just try to run this command-line manually > > > > and see what the problem is on a bare shell. > > > > > > > > D. > > > > > > > > On Fri, Aug 6, 2021 at 6:44 PM Michael Sokolov <[email protected]> > > > > wrote: > > > > > > > > > > Hi all, does anybody have helpful tips about how to chase down > > > > > javadoc build failures? I made some new stuff, and ./gradlew test > > > > > passes, but ./gradlew check fails with this less than fully > > > > > explanatory message: > > > > > > > > > > $ JAVA_HOME=/usr/lib/jvm/java-1.11.0-openjdk-amd64/ ./gradlew check > > > > > > Task :lucene:core:renderJavadoc FAILED > > > > > > > > > > FAILURE: Build failed with an exception. > > > > > > > > > > * Where: > > > > > Script > > > > > '/home/ANT.AMAZON.COM/sokolovm/workspace/lucene/gradle/documentation/render-javadoc.gradle' > > > > > line: 450 > > > > > > > > > > * What went wrong: > > > > > Execution failed for task ':lucene:core:renderJavadoc'. > > > > > > No value present > > > > > > > > > > * Try: > > > > > Run with --stacktrace option to get the stack trace. Run with --info > > > > > or --debug option to get more log output. Run with --scan to get full > > > > > insights. > > > > > > > > > > * Get more help at https://help.gradle.org > > > > > > > > > > BUILD FAILED in 3s > > > > > 44 actionable tasks: 17 executed, 27 up-to-date > > > > > > > > > > --------------------------------------------------------------------- > > > > > 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] > > > > > > > > > > --------------------------------------------------------------------- > > > 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] > > > > --------------------------------------------------------------------- > 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]
