forked from KeepSafe/dexcount-gradle-plugin
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Revert KeepSafe#32 and remove
@Input
from apkOrDex
This fixes a bug wherein the dexcount task fails if the variant's output is renamed after the dexcount plugin is applied and prior to task execution. This also opts dexcount out of Gradle's incremental compilation cache. The proximate cause of this bug is that we're holding a stale `java.io.File` object; the cure is to instead hold a reference to the variant's output. This doesn't work with incremental compliation, because variant output implementations aren't `Serializable` (noted in KeepSafe#32), and Gradle depends on task state being serializable. This mismatch means that dexcount will appear to randomly crash. The least-bad solution is to just remove the task-input annotation, and run the count task every time. Not great, but better than not working. Fixes KeepSafe#40 and KeepSafe#46.
- Loading branch information
1 parent
28d1210
commit d257189
Showing
4 changed files
with
10 additions
and
6 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters