From 1d35ca03b8a1c431937a9be74a9efedc15b5707a Mon Sep 17 00:00:00 2001 From: Dan Fabulich Date: Thu, 5 Jul 2018 16:08:06 -0700 Subject: Replace instances of Blaze with Bazel. PiperOrigin-RevId: 203300374 Change-Id: Iaa47f870ab2e0cad40a202aad2c7f9430f73c856 PiperOrigin-RevId: 203407392 --- .../google/devtools/build/lib/rules/android/AndroidDeviceRule.java | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'src/main/java/com/google/devtools/build/lib/rules/android/AndroidDeviceRule.java') diff --git a/src/main/java/com/google/devtools/build/lib/rules/android/AndroidDeviceRule.java b/src/main/java/com/google/devtools/build/lib/rules/android/AndroidDeviceRule.java index 666840bda0..05356e5e15 100644 --- a/src/main/java/com/google/devtools/build/lib/rules/android/AndroidDeviceRule.java +++ b/src/main/java/com/google/devtools/build/lib/rules/android/AndroidDeviceRule.java @@ -181,11 +181,11 @@ public final class AndroidDeviceRule implements RuleDefinition { /*

This rule creates an android emulator configured with the given - specifications. This emulator may be started via a blaze run + specifications. This emulator may be started via a bazel run command or by executing the generated script directly. It is encouraged to depend on existing android_device rules rather than defining your own.

-

This rule is a suitable target for the --run_under flag to blaze test and blaze +

This rule is a suitable target for the --run_under flag to bazel test and blaze run. It starts an emulator, copies the target being tested/run to the emulator, and tests it or runs it as appropriate.

@@ -229,7 +229,7 @@ ro.product.name=soju

This rule will generate images and a start script. You can start the emulator - locally by executing blaze run :nexus_s -- --action=start. The script exposes + locally by executing bazel run :nexus_s -- --action=start. The script exposes the following flags: