Skip to content

Commit ff1bdd3

Browse files
authored
Merge pull request #118 from runningcode/no/readme-update
README update
2 parents 44c4a7a + 63c9c2c commit ff1bdd3

File tree

1 file changed

+21
-3
lines changed

1 file changed

+21
-3
lines changed

README.md

Lines changed: 21 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,20 +5,27 @@
55
Some Android plugin versions have issues with Gradle's build cache feature. When applied to an Android project this plugin applies workarounds for these issues based on the Android plugin and Gradle versions.
66

77
* Supported Gradle versions: 5.4.1+
8-
* Supported Android versions: 3.5.4, 3.6.4, 4.0.1, 4.1.0-beta05, 4.2.0-alpha07
8+
* Supported Android versions: 3.5.4, 3.6.4, 4.0.1, 4.1.0-rc01, 4.2.0-alpha07
99
* Supported Kotlin versions: 1.3.70+
1010

1111
We only test against the latest patch versions of each minor version of Android Gradle Plugin. This means that although it may work perfectly well with an older patch version (say 3.6.2), we do not test against these older patch versions, so the latest patch version is the only version from that minor release that we technically support.
1212

13+
## Should I use this?
14+
Take a look at the [list of issues](#list-of-issues) especially [unresolved issues](#unresolved-issues). If any of these apply to your project, you can use this plugin to solve them.
15+
16+
## How can I discover issues?
17+
You can discover issues by using the task input comparison tool in Gradle Enterprise. More information about [how to diagnose cache misses here](https://docs.gradle.com/enterprise/tutorials/task-inputs-comparison/). You can compare the inputs of a build that seeds the build cache - typically CI - with a build that consumes from the build cache like a local developer build.
18+
If you discover an issue related to the Android Gradle Plugin, please file an issue in the [Android Bug Tracker](https://source.android.com/setup/contribute/report-bugs). You can also file an [issue here](https://github.com/gradle/android-cache-fix-gradle-plugin/issues) and we can see if a workaround is possible.
19+
1320
## Applying the plugin
1421

1522
This plugin should be applied anywhere the `com.android.application` or `com.android.library` plugins are applied. Typically,
16-
this can just be injected from the root project's build.gradle (change '1.0.9' to the latest version of the cache fix plugin
23+
this can just be injected from the root project's build.gradle (change '1.0.10' to the latest version of the cache fix plugin
1724
[here](https://plugins.gradle.org/plugin/org.gradle.android.cache-fix)):
1825

1926
``` groovy
2027
plugins {
21-
id "org.gradle.android.cache-fix" version "1.0.9" apply false
28+
id "org.gradle.android.cache-fix" version "1.0.10" apply false
2229
}
2330
2431
subprojects {
@@ -39,3 +46,14 @@ static class AndroidJavaCompile_BootClasspath_Workaround implements Workaround {
3946
// ...
4047
}
4148
```
49+
50+
### Unresolved Issues
51+
52+
The following caching issues are fixed by the cache fix plugin but unresolved in any current or upcoming preview release of the Android Gradle Plugin as of 21.08.2020.
53+
54+
Please star them if you are experiencing them in your project.
55+
56+
* CompileLibraryResourcesTask is not relocatable: https://issuetracker.google.com/issues/155218379
57+
* DexFileDependenciesTask is not cacheable: https://issuetracker.google.com/160138798
58+
* MergeResources is not relocatable: https://issuetracker.google.com/issues/141301405
59+
* Room annotation processor causes cache misses, doesn't declare outputs, overlapping outputs, etc: https://issuetracker.google.com/issues/132245929

0 commit comments

Comments
 (0)