This message was deleted.
# general
s
This message was deleted.
b
I do, never had issues with IJ nor AS detecting sdkman SDKs
e
So I did gradle --stop. I run gradle build in AS. I opened terminal and just run gradle tasks in it. I saw a new daemon start. I also see that I have two daemons now.
b
Ah, that's a separate issue. IJ is not running in the same env as your shell, so variables might be different
Check which jvm ij gradle is set to use in ij settings
e
That is what I wrote in m first message
The suspicion that it is path to JVM, however there might be other things that make daemon not compatible
b
I know, that's why I'm saying that you're probably not injecting sdkman variables at low-enough level. In any case, you can set IJ env variables in the settings if you don't want to fiddle with your SYS login script layers
Also by this
Check which jvm ij gradle is set to use in ij settings
I did not mean via the terminal. Literally go to IJ settings and find gradle section to see which JVM it is set to use
Most of the time it defaults to project SDK, but not always
e
Yup, I’ve been there many times. Here is mine
b
And your gradle runs via IJ still don't use that?
Have you tried setting JAV_HOME here? This is suboptimal, but at least avoids you tinkering with
/etc/environment
e
I tried to duplicate JAVA_HOME there and paste symlink. Whenever I pressed save - it was resolved.
BTW, gradle picks the correct JDK
The only issue it runs one more daemon and don’t reuse one that started from terminal
b
Oh, my bad. NOW I get you issue 🤦‍♂️ Different JDK path is breaking reuse of the gradle daemon, even though it's exactly the same JDK, right?
In that case I think I also have the same issue. I guess the best place to have it fixed would be on gradle daemon side to also resolve symlinks before checking daemon compatability.
Apologies for walking you in circles...
e
Thank you for the conversation, and no issues!
Actually let me know if you have the same issue
b
I do! I think everyone does and will keep having until symlinks are taken resolved out of the daemon compatability checks
e
I probably will create ticket on the Gradle GH
👍 1