New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
hiltJavaCompile task loads deprecated annotation processors #4116
Comments
That's right, the HiltGradlePlugin will configure the annotation processor classpath of the There are some options we can do here, but they all have some sort of pros-cons:
|
How can I suppress this specific error when |
I think you'll have better luck asking on StackOverflow. |
We migrated our project to 100% KSP (Hilt 1.1.0-rc01, Room 2.6.0, Moshi 1.15.0) and removed all usages of kapt. Still we see a deprecation warning which should only be shown if the deprecated Moshi Code Gen Annotation Processor is being loaded into kapt/apt. See this build log from a minimal reproducible example project: https://github.com/G00fY2/HiltMoshiKaptWarning/actions/runs/6683702355/job/18160177116#step:5:44
I started a discussion in the Moshi project to make sure that this is not something wrong on Moshi's side: square/moshi#1752
@ZacSweers pointed out in that discussion that
hiltJavaCompile
task is capturing all KSP and kapt dependencies and passing them on to the JavaCompile task it creates. This causes the actually unused Code Gen Processor to print a deprecation warning.Not sure what's the reason behind this. But would be nice if dagger/hilt would not load these classes and potentially mislead users.
The text was updated successfully, but these errors were encountered: