-
Notifications
You must be signed in to change notification settings - Fork 174
/
Copy pathAnnotationProcessorOnCompilePath.md.html
143 lines (124 loc) · 5.7 KB
/
AnnotationProcessorOnCompilePath.md.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
<meta charset="utf-8">
(#) Annotation Processor on Compile Classpath
!!! WARNING: Annotation Processor on Compile Classpath
This is a warning.
Id
: `AnnotationProcessorOnCompilePath`
Summary
: Annotation Processor on Compile Classpath
Severity
: Warning
Category
: Performance
Platform
: Android
Vendor
: Android Open Source Project
Feedback
: https://issuetracker.google.com/issues/new?component=192708
Since
: 3.6.0 (February 2020)
Affects
: Gradle build files
Editing
: This check runs on the fly in the IDE editor
Implementation
: [Source Code](https://cs.android.com/android-studio/platform/tools/base/+/mirror-goog-studio-main:lint/libs/lint-checks/src/main/java/com/android/tools/lint/checks/GradleDetector.kt)
Tests
: [Source Code](https://cs.android.com/android-studio/platform/tools/base/+/mirror-goog-studio-main:lint/libs/lint-tests/src/test/java/com/android/tools/lint/checks/GradleDetectorTest.kt)
This dependency is identified as an annotation processor. Consider
adding it to the processor path using `annotationProcessor` instead of
including it to the compile path.
!!! Tip
This lint check has an associated quickfix available in the IDE.
(##) Example
Here is an example of lint warnings produced by this check:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~text
build.gradle:2:Warning: Add annotation processor to processor path using
annotationProcessor instead of api [AnnotationProcessorOnCompilePath]
api 'com.jakewharton:butterknife-compiler:10.1.0'
---
build.gradle:3:Warning: Add annotation processor to processor path using
annotationProcessor instead of implementation
[AnnotationProcessorOnCompilePath]
implementation 'com.github.bumptech.glide:compiler:4.9.0'
--------------
build.gradle:4:Warning: Add annotation processor to processor path using
annotationProcessor instead of compile
[AnnotationProcessorOnCompilePath]
compile "androidx.lifecycle:lifecycle-compiler:2.2.0-alpha01"
-------
build.gradle:5:Warning: Add annotation processor to processor path using
testAnnotationProcessor instead of testImplementation
[AnnotationProcessorOnCompilePath]
testImplementation "com.google.auto.value:auto-value:1.6.2"
------------------
build.gradle:6:Warning: Add annotation processor to processor path using
androidTestAnnotationProcessor instead of androidTestCompile
[AnnotationProcessorOnCompilePath]
androidTestCompile "org.projectlombok:lombok:1.18.8"
------------------
build.gradle:8:Warning: Add annotation processor to processor path using
debugAnnotationProcessor instead of debugCompile
[AnnotationProcessorOnCompilePath]
debugCompile "android.arch.persistence.room:compiler:1.1.1"
------------
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Here is the source file referenced above:
`build.gradle`:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~groovy linenumbers
dependencies {
api 'com.jakewharton:butterknife-compiler:10.1.0'
implementation 'com.github.bumptech.glide:compiler:4.9.0'
compile "androidx.lifecycle:lifecycle-compiler:2.2.0-alpha01"
testImplementation "com.google.auto.value:auto-value:1.6.2"
androidTestCompile "org.projectlombok:lombok:1.18.8"
annotationProcessor 'com.jakewharton:butterknife-compiler:10.1.0'
debugCompile "android.arch.persistence.room:compiler:1.1.1"
implementation "com.jakewharton:butterknife:10.1.0"
}
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
You can also visit the
[source code](https://cs.android.com/android-studio/platform/tools/base/+/mirror-goog-studio-main:lint/libs/lint-tests/src/test/java/com/android/tools/lint/checks/GradleDetectorTest.kt)
for the unit tests for this check to see additional scenarios.
The above example was automatically extracted from the first unit test
found for this lint check, `GradleDetector.testAnnotationProcessorOnCompilePath`.
To report a problem with this extracted sample, visit
https://issuetracker.google.com/issues/new?component=192708.
(##) Suppressing
You can suppress false positives using one of the following mechanisms:
* Using a suppression comment like this on the line above:
```kt
//noinspection AnnotationProcessorOnCompilePath
problematicStatement()
```
* Using a special `lint.xml` file in the source tree which turns off
the check in that folder and any sub folder. A simple file might look
like this:
```xml
<?xml version="1.0" encoding="UTF-8"?>
<lint>
<issue id="AnnotationProcessorOnCompilePath" severity="ignore" />
</lint>
```
Instead of `ignore` you can also change the severity here, for
example from `error` to `warning`. You can find additional
documentation on how to filter issues by path, regular expression and
so on
[here](https://googlesamples.github.io/android-custom-lint-rules/usage/lintxml.md.html).
* In Gradle projects, using the DSL syntax to configure lint. For
example, you can use something like
```gradle
lintOptions {
disable 'AnnotationProcessorOnCompilePath'
}
```
In Android projects this should be nested inside an `android { }`
block.
* For manual invocations of `lint`, using the `--ignore` flag:
```
$ lint --ignore AnnotationProcessorOnCompilePath ...`
```
* Last, but not least, using baselines, as discussed
[here](https://googlesamples.github.io/android-custom-lint-rules/usage/baselines.md.html).
<!-- Markdeep: --><style class="fallback">body{visibility:hidden;white-space:pre;font-family:monospace}</style><script src="markdeep.min.js" charset="utf-8"></script><script src="https://morgan3d.github.io/markdeep/latest/markdeep.min.js" charset="utf-8"></script><script>window.alreadyProcessedMarkdeep||(document.body.style.visibility="visible")</script>