Arunkumar

This was blocked by https://github.com/google/dagger/issues/3483. Now that is implemented in Dagger, I will try to display component dependencies differently.

Thanks for the update, closing this please reopen if anything comes up.

Seems addressed by https://github.com/bazelbuild/bazel/commit/10af780af88b794c1497e771c6d8bab925297c3c so closing this. However the https://github.com/bazelbuild/bazel/issues/13639 absolute path issue still remains

Was looking through Google's Kotlin bazel implementation and came across [this](https://cs.android.com/android-studio/platform/tools/base/+/mirror-goog-studio-main:bazel/src/com/android/tools/kotlin/KotlinCompiler.java;l=59) which potentially can help? ```kotlin private static void clearJarCache() { // This is adapted from CompileServiceImpl.clearJarCache in the Kotlin...

Hello thanks for raising this, will fix this for next release.

Hey @sylwek845 thanks for reporting this. Adding a bit of context for this behavior, this is due to the fact that Grazel tries to do incremental migration by default. We...

Thanks for reporting, may I know the Dagger version you are using and if upgrading Dagger fixes it?

Related https://github.com/bazelbuild/rules_jvm_external/issues/909

w.r.t `androidx.annotation` issue, this can be temporarily worked around by adding a `override_target` that maps `annotation` to `annotation-jvm` Like done [here](https://github.com/grab/grazel/blob/ecbe062caa81c93a41dc055eeac5d1d04ceee30c/WORKSPACE#L126) ``` override_targets = { "androidx.annotation:annotation": "@maven//:androidx_annotation_annotation_jvm", }, ```

Thanks for trying out, currently we are primarily focusing on Android although there will be limited support for `java_library` and `kt_jvm_library`.