IssueTracker

I get the same error on a freshly downloaded 2020.3.1.4 extracted into /usr/local/google/home/sgjesse/android-studio/2020.3.1.4:

Execution failed for task ':app:compileDebugJavaWithJavac'.
> Could not resolve all files for configuration ':app:androidJdkImage'.
   > Failed to transform core-for-system-modules.jar to match attributes {artifactType=_internal_android_jdk_image, org.gradle.libraryelements=jar, org.gradle.usage=java-runtime}.
      > Execution failed for JdkImageTransform: /usr/local/google/home/sgjesse/Android/Sdk/platforms/android-30/core-for-system-modules.jar.
         > jlink executable /usr/local/google/home/sgjesse/android-studio/2020.3.1.4/jre/bin/jlink does not exist.

I don't see and jlink executable in /usr/local/google/home/sgjesse/android-studio/2020.3.1.4/jre/bin:

ls /usr/local/google/home/sgjesse/android-studio/2020.3.1.4/jre/bin
jaotc  javac    jdb  jhsdb  jrunscript  pack200  rmiregistry  unpack200
java   javadoc  jfr  jjs    keytool     rmid     serialver

seems like we require JDK binaries while Android Studio points us to a JRE.

is there a /usr/local/google/home/sgjesse/android-studio/2020.3.1.4/bin folder in your installation ?

ls /Applications/Android\ Studio\ Preview.app/Contents/jre/jdk/Contents/Home/bin
jaotc		javadoc		jhsdb		keytool		rmiregistry
java		jdb		jjs		pack200		serialver
javac		jfr		jrunscript	rmid		unpack200

Modifying the field File->Project Structure->SDK Location->JRE Location to point to a full JDK 11 (which includes bin/jlink) fixes the issue.

For building directly with gradlew a JDK 11 JDK has to be located either through org.gradle.java.home in gradle.properties, the JAVA_HOME environment variable or the java command first in the PATH (in that order of precedence).

Raluca, it seems that our prebuilts/studio/jdk/jdk11-runtime is missing jlink. Is this by design?

Is this fixed?

Seeing the same issue in alpha11.

Setting this a blocking the next canary, as it impacts usage of java 11 language features in 7.0.

Until it is fixed, please use the workaround from #6.

Fixed for Arctic Fox Canary 14

I hit the same issue in Flamingo with the following in build.gradle.kts (from Tivi):

plugins.withType<JavaBasePlugin>().configureEach {
    extensions.configure<JavaPluginExtension> {
        toolchain {
            languageVersion.set(JavaLanguageVersion.of(11))
        }
    }
}

The workaround in comment #6 no longer seems to work since Gradle requires Java 17. I instead fixed the problem by adding custom toolchain locations as described in https://docs.gradle.org/current/userguide/toolchains.html#sec:custom_loc:

org.gradle.java.installations.paths=/path/to/jdk11,/path/to/jdk17

re @16, does it work with Arctic Fox Canary 14?

re: comment#16, AFAICT, we bundle jlink in our 17 runtime as well.

From debugging the issue with Christoffer yesterday I think the issue is that explicitly setting the toolchain to JDK-11 (that Tivi use, comment #16) cause Gradle to use its logic for preferred JDK (https://docs.gradle.org/current/userguide/toolchains.html#sec:precedence) to look for a JDK-11 (thereby not using the JDK-17 shipped with Android Studio for parts of the build). On the gLinux installation where this happened Gradle ended up finding a JRE-11 (not JDK-11), which does not include jlink. Setting org.gradle.java.installations.paths explicitly to both a JDK-11 and a JDK-17 solved the issue.

The main issue here is that this is quite difficult to figure out, and the Gradle documentation spends a lot of time on its automatic discovery and automatic download leaving the explanation of the explicit configuration to the very end. If the use of explicit toolchain are commonly used maybe Studio should ship with multiple JDKs and not depend on local system configuration of the most commonly uses JDKs.

Setting org.gradle.java.installations.paths and shipping multiple JDKs would definitly helps Gradle to find the right JDK, but it seems we cannot guarantee the right one would be picked because Gradle does not prioritize custom toolchains over auto-detected toolchains. Maybe we can start having a better error message in the transform if the users is using a JRE instead of JDK or the JDK doesn't have the jlink.

Yes you are right, we actually also added org.gradle.java.installations.auto-detect=false, which was not mentioned in comment #16.

For posterity, because this ranks high on Google, even though the problem might not be exactly the same.

I got the same error on AGP 8.2.1. Here are some quick learnings:

• gradlew :javaToolchains is godsent when it comes to diagnosing these issues.
• JDK 8 doesn't have jlink, because jlink is a tool for the JMS (Java Module System) introduced in Java 9.
• Make sure you have "org.gradle.toolchains.foojay-resolver-convention" or other provider for Gradle set up.
• Make sure android.compileOptions.sourceCompatibility <= java.toolchain.languageVersion, otherwise the error in #1 could come up.