-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Create standalone annotations artifact for AutoFactory #631
Comments
This seems like a trivial issue and triggers most of warnings on our builds, can I offer my help? |
Also, it's a dupe of #632 |
it was done with https://github.com/JakeWharton/AutoValueAnnotations - it would be cool to have it here in original Api and it's seems to be quite easy as there is no need of change actual code, just generating and publishing artefacts - hope it will be available soon - especially now when gradle force you to declare annotationProcessors explicitly in gradle config |
@filipkowicz https://github.com/google/auto/releases/tag/auto-value-1.6 Wrt your Grade comment, for auto-service or auto-factory, just declare the same dependency in both |
@tbroyer it's great but it's for according to gradle: I'm currently doing it this way but:
so yes - currently it works but it could be a lot nicer and there is no point of adding classes from annotation processor to classpath during compile |
I updated to Android Studio 3.6 Canary 12 and there is a (new?) Lint check called dependencies {
compileOnly("com.google.auto.factory:auto-factory:$versions.autoFactory") {
transitive = false
}
kapt "com.google.auto.factory:auto-factory:$versions.autoFactory"
} |
This was done for AutoValue (#268) and should also be done for AutoFactory.
The text was updated successfully, but these errors were encountered: