IssueTracker

(Extracted from http://issuetracker.google.com/212674413#comment16.)

Steps to reproduce

1. Open a simple project with a build-logic included build (see attached)

2. Run ps ax | grep GradleDaemon and take note of the Gradle daemons and their versions (run ./gradlew --stop if necessary)

3. Run Clean Project from Android Studio

4. Run ps ax | grep GradleDaemon again. Observe that there are multiple Gradle daemons with different versions (one is the Gradle wrapper version specified in the project, and the other is the Gradle Tooling API version that Android Studio uses).

Expected behavior

Only 1 Gradle daemon should be launched, with the version specified in the project.

Potential root cause

The relevant code seems to be at GradleBuildInvokerImpl.kt:

// Collect the root project path for all modules, there is one root project path per included project.
val projectRootPaths: Set<File> =
      ModuleManager.getInstance(project).modules.mapNotNull { module -> module.getGradleProjectPath()?.buildRoot?.let(::File) }.toSet()
return combineGradleInvocationResults(
      projectRootPaths
        .map { projectRootPath -> executeTasks(CLEAN, projectRootPath, Collections.singletonList(CLEAN_TASK_NAME)) }
)

This is roughly equivalent to running:

1. ./gradlew clean
2. cd build-logic && ./gradlew clean // build-logic is the included project

Since there is no Gradle version specified in the build-logic included project, Gradle will start a new daemon with the version of the Gradle Tooling API that is being used.

Workaround

Copy gradle/wrapper/gradle-wrapper.jar and gradle/wrapper/gradle-wrapper.properties from the main project to the included project. This will allow Gradle to use the version specified in the included project, which is now the same as the main project.

Also copy gradle.properties from the main project to the included project too. This is so that Gradle can reuse the same daemon, otherwise there would be 2 Gradle daemons having the same version.