IssueTracker

Warning message was changed

The new message is like this:

  Android Studio is using the following JDK location when running Gradle:
  ${jdkPath}
  Using different JDK locations on different processes might cause Gradle to
  spawn multiple daemons, for example, by executing Gradle tasks from a terminal
  while using Android Studio.

The original message was intended to be a warning when AS suspects that it is using a different JDK to the one used while running Gradle in the CLI. Changing the JDK on the Project Structure dialog has no effect on how Gradle is run from the CLI. If you want to modify what JDK is used, then you can change it by modifying JAVA_HOME in a terminal and run it from there or set it up in one of the Gradle files (https://docs.gradle.org/current/userguide/build_environment.html).

It is possible that some of your coworkers in comment #6 are no longer seeing the warning after they disregarded the message and clicked the do not show again option. You can confirm if that is the case by going to Settings -> Appearance & Behavior -> Notifications and look for the "JDK Location different to JAVA_HOME" group.

It tries to generate a new process with its own environment and from there it uses JAVA_HOME, if that is not defined then it uses java.home from the java system properties.

It changes depending on the OS version and the application used as terminal, even for default configurations on different versions of Mac OS. So instead of trying to guess we show that more generic message and use the current environment. There are many possible ways Gradle can be run and there is not a reliable way that AS can check if there will be issues when running other processes.

This warning must be considered just as a reminder that multiple daemons could be running and that this could be one of the causes. Having a different JDK it is not a problem by itself, so hence the warning and that is why it can be disabled.