rules_kotlin: Android rules not working properly with exported Java plugins

Following Dagger’s recommended Hilt integration, when using this android_library target with the following Java class, the code generation runs fine:

android_library(
    name = "app",
    srcs = ["SampleApplication.java"],
    manifest = "AndroidManifest.xml",
    deps = [
        ":res",
        "//third_party/dagger/hilt:hilt-android",
    ],
)

package fr.enoent.android.sample;

import android.app.Application;
import dagger.hilt.android.HiltAndroidApp;

@HiltAndroidApp(Application.class)
public class SampleApplication extends Sample_BurgApplication {
}

The exact same set-up with a kt_android_library, however, doesn’t end up calling the plugins exported by //third_party/dagger/hilt:hilt-android at all. Even when only passing the same Java file to kt_android_library - the compilation fails because the generated superclass isn’t generated.

From there, I tried passing the plugins explicitly to the kt_android_library’s plugins attribute. With a Java file, they don’t seem to run at all either (maybe expected?). With a Kotlin file, some seem to run, but either not all or not in the correct order, I’m really not familiar enough with annotation processors to understand what’s going on there - one of the Hilt plugins fails because the superclass hasn’t been generated.

I’m not sure how much of that is working as intended, but it’s a strong behavioural difference from the native android_library (and I believe kt_jvm_library as well?).