https://gradle.com/ logo
Join Slack
Powered by
This message was deleted.
# community-support
s
This message was deleted.
v
If you run with 
--stacktrace
you should see where this warning is coming from.
e
Unless I am mistaken, nothing in the stack trace points to our code?! I can't post the stacktrace here, because it is 14000something chars to long 😉
v
Attach it as file, or use some paste service like gist.github.com or pastebin.com
✅ 1
e
Here we go
trace.txt
v
Ah, bad, it's lazy evaluated and validated, so you don't see where it is set in the stack trace. I guess easiest would be to set a breakpoint. Either to 
Property#set
, testing for the Semeru argument, or maybe to 
getVendor
.
e
Is there documentation how to do that on the command line?
v
Why from the command line?
e
Well, I have no zero experience running gradle with debugger/breakpoints, so I had hoped there is an easy to do it like that. Our gradle build does work in IntelliJ, but I rarely run tasks from there.
v
But that's indeed the easiest. You just set your breakpoints and use "Debug" in IntelliJ, that's it. Easy as pie
e
I will try later then; right now I am busy fixing the configuration cache issues 😉
👌 1
Yes, it is actually pretty easy, but I am still confused. I put a breakpoint into org/gradle/jvm/toolchain/internal/DefaultToolchainSpec :: isValid() ... and I can see that (obviously) that path is taken, but the Vendor object says IBM?!
But that's the nice thing when you are in your IDE; jumping into the JvmVendorSpec class ... it doesn't come as surprise now that IBM == IBM_SEMERU ... when the one is directly derived from the other 😉 Do I need to write a bug report now?
Copy code
IBM = matching(KnownJvmVendor.IBM);
IBM_SEMERU = IBM;
v
Seems so, yes
e
👍
7 Views
Open in Slack
PreviousNext
Powered by