Reflect progress on incremental dexing in android_binary's incremental_dexing attribute documentation.
RELNOTES: None.
@@ -811,13 +811,8 @@ public final class AndroidRuleClasses {
<!-- #END_BLAZE_RULE.ATTRIBUTE --> */
.add(attr("dex_shards", INTEGER).value(1))
/* <!-- #BLAZE_RULE($android_binary_base).ATTRIBUTE(incremental_dexing) -->
- Force the target to be built with or without incremental dexing, overriding defaults and
- --incremental_dexing flag. Users should set this attribute to 0 for release binaries
- (e.g., to avoid accidental usage of --incremental_dexing), since incremental dexing can
- produce slightly larger artifacts than dx. It is an error to set this attribute to 1 for
- android_binary and android_test rules that have Proguard enabled, as well as for
- android_test rules with binary_under_test set. We are working on addressing these
- shortcomings so please check with us if you run into these limitations.
+ Force the target to be built with or without incremental dexing, overriding defaults
+ and --incremental_dexing flag.
<!-- #END_BLAZE_RULE.ATTRIBUTE --> */
.add(
attr("incremental_dexing", TRISTATE)
