From cf03c3dc8971588e2d5deb9831f2843fd39a2f6e Mon Sep 17 00:00:00 2001 From: kmb Date: Wed, 20 Sep 2017 21:35:26 +0200 Subject: remove long-deprecated incremental dexing flag that has no effect RELNOTES: remove unused --host_incremental_dexing flag PiperOrigin-RevId: 169433775 --- .../build/lib/rules/android/AndroidConfiguration.java | 13 ------------- 1 file changed, 13 deletions(-) (limited to 'src/main/java') diff --git a/src/main/java/com/google/devtools/build/lib/rules/android/AndroidConfiguration.java b/src/main/java/com/google/devtools/build/lib/rules/android/AndroidConfiguration.java index 49d9e0954f..44d74ff44d 100644 --- a/src/main/java/com/google/devtools/build/lib/rules/android/AndroidConfiguration.java +++ b/src/main/java/com/google/devtools/build/lib/rules/android/AndroidConfiguration.java @@ -400,19 +400,6 @@ public class AndroidConfiguration extends BuildConfiguration.Fragment { ) public boolean incrementalDexing; - // TODO(b/31711689): remove this flag from config files and here - @Option( - name = "host_incremental_dexing", - defaultValue = "false", - metadataTags = {OptionMetadataTag.HIDDEN}, - documentationCategory = OptionDocumentationCategory.UNDOCUMENTED, - effectTags = {OptionEffectTag.UNKNOWN}, - help = - "This flag is deprecated in favor of applying --incremental_dexing to both host " - + "and target configuration. This flag will be removed in a future release." - ) - public boolean hostIncrementalDexing; - // Do not use on the command line. // The idea is that this option lets us gradually turn on incremental dexing for different // binaries. Users should rely on --noincremental_dexing to turn it off. -- cgit v1.2.3