Eager configuration of Tasks produces incorrect compiler arguments for HiltJavaCompile

[cdsap]

Hi, thanks for the plugin.

In a project using Hilt, kapt and Databinding, we noticed that Hilt tasks were causing overlapping outputs in the Gradle builds:

We analyzed the different possible causes and we found that Hilt is copying the compiler arguments of the original compile task: https://github.com/google/dagger/blob/master/java/dagger/hilt/android/plugin/main/src/main/kotlin/dagger/hilt/android/plugin/HiltGradlePlugin.kt#L384
This action should be correct, however given the following scenario:

• Databinding
• Kapt
• Hilt
• Java >=9

an eager configuration of the JavaCompile tasks produces Hilt tasks with compiler arguments of databinding:

This situation makes the hilt tasks no cacheable.

I created this repository: https://github.com/cdsap/HiltDatabindingIssue to reproduce the issue.
The action that triggers the early task configuration is:
https://github.com/cdsap/HiltDatabindingIssue/blob/main/app/build.gradle#L56

I'm not sure is Hilt bug, but I found interesting to share with you

[kuanyingchou]

Hi, @cdsap , thanks for creating the issue and the repro. I can reproduce this on my side, but still need more time to figure out the problem. I will update you as soon as possible.