IssueTracker

Ying, can you take a look?

It seems like when trying to run a class we trigger a build and inject a gradle file via --init-script ?

There are several issues here:

(1) this is a duplicate of https://issuetracker.google.com/241686649 (refreshing the VFS fixes the problem in simple cases)

(2) however, I believe Android modules might not expose the full runtime classpath to the IDE and thus there might still be missing classes in some cases.

The issue is in the generated init script that's used in the TAPI invocation:

    def gradlePath = ':app'
    def runAppTaskName = 'Data.main()'
    def mainClass = 'com.example.myapplication.Data'
    def javaExePath = mapPath('/usr/local/google/home/gavra/.jdks/temurin-17.0.3/bin/java')
    def _workingDir = mapPath('/usr/local/google/home/gavra/AndroidStudioProjects/MyApplication86')

    def sourceSetName = 'main'
    def javaModuleName = null

    import org.gradle.util.GradleVersion

    allprojects {
      afterEvaluate { project ->
        if(project.path == gradlePath && project?.convention?.findPlugin(JavaPluginConvention)) {
          def overwrite = project.tasks.findByName(runAppTaskName) != null
          project.tasks.create(name: runAppTaskName, overwrite: overwrite, type: JavaExec) {
            if (javaExePath) executable = javaExePath
            main = mainClass
            
            if (_workingDir) workingDir = _workingDir
            standardInput = System.in
            if (javaModuleName) {
              classpath = tasks[sourceSets[sourceSetName].jarTaskName].outputs.files + project.sourceSets[sourceSetName].runtimeClasspath;
              if (GradleVersion.current().baseVersion < GradleVersion.version("6.4")) {
                doFirst {
                  jvmArgs += [
                    '--module-path', classpath.asPath,
                    '--module', javaModuleName + '/' + mainClass
                  ]
                  classpath = files()
                }
              } else {
                mainModule = javaModuleName
              }
            } else {
              classpath = project.sourceSets[sourceSetName].runtimeClasspath
            }
          }
        }
      }
    }
    

this script is able to handle only java projects.

We should remove the run configurations for main from the gutter in Android modules, and the recommended way to accomplish #1 is to:

• create a non-Android (i.e. java or kotlin) module and add the main() method there
• add an Android module that depends on the java/kotlin library
• start using APIs from the library in the Android module.

Bradley can you please take a look at hiding the run configurations?

Why does this script not work for Android modules? What in 3.6 broke this? Can we generalize the script or make changes to AGP so that it does work?

The script relies on the Java plugin source sets, jar tasks etc. that are not applicable for Android projects. WRT AS 3.6, I did not verify if it was working in that version nor what changed. Can you please check?

It is definitely possible to trigger full compilation in an Andorid Gradle project, compute the full runtime classpath, and specify the correct args for JavaExec. Challenge here is writing it in a way that works with all AGP versions, and that is definitely a non-trivial effort. The workaround from #5 seems like a very low-friction solution, so I recommend users to use it as a way to run main, and we should hide the run configuration from the gutter.

This will require an update from JetBrains, and I have filed an bug and working on a change there: link

I have checked in the fix for this on the JetBrains side. It will take some time for this IJ version to be available to Android. Once it is, I will create the fix for Android and update here.