Fixed
Status Update
Comments
xa...@google.com <xa...@google.com> #2
This was broken by 3bca759a5ff08352de831bb1e9b61b1ec2b3362d.
Fix (pending) is I2c2dc7b600603ee430fd0d91b23d52ea8aa29ca9.
Fix (pending) is I2c2dc7b600603ee430fd0d91b23d52ea8aa29ca9.
xa...@google.com <xa...@google.com> #3
Almost 2 months later and this is still broken
ga...@google.com <ga...@google.com> #4
Since there is no progression, I wanted to share our quick-fix for the issue.
#sdkmanager --package_file=${PATH_WORKSPACE}/packages
while read p; do echo "y" | sdkmanager "${p}"; done <${PATH_WORKSPACE}/packages
#sdkmanager --package_file=${PATH_WORKSPACE}/packages
while read p; do echo "y" | sdkmanager "${p}"; done <${PATH_WORKSPACE}/packages
an...@google.com <an...@google.com> #6
What is the status of this item?
fi...@gmail.com <fi...@gmail.com> #7 Restricted+
Restricted+
Comment has been deleted.
wi...@gmail.com <wi...@gmail.com> #8 Restricted
Restricted
Comment has been deleted.
Description
The
JavaPreCompileTask
computes KSP and annotation processors that are consumed in downstreamJavaCompile
tasks. For annotation processors, the compilation task in AGP computes if any processors are non-incremental, and (correctly) reports a warning for any non-incremental processors found.However, there's a bug in
JavaPreCompileTask
's logic as it merges the KSP and annotation processing classpath when computing, meaning that dependencies on the KSP classpath are incorrectly treated as if they are going to be on the JavaCompileannotationProcessorClasspath
.Essentially, in this bit of logic
It shouldn't be merging together the ksp and annotation processor artifacts, as KSP dependencies do not participate in the
JavaCompile
classpath.In the meantime, I can work around this with the following snippet in Kotlin gradle DSL.