Add rules.aar

third_party/android_support_test_runner/BUILD.gn

 # Copyright 2016 The Chromium Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
 import("//build/config/android/rules.gni")
 
 android_java_prebuilt("runner_java") {
   jar_path = "lib/runner-0.3-release-no-dep.jar"
   deps = [
+    ":exposed_instrumentation_api_publish_java",
     "//third_party/guava:guava_java",
+    "//third_party/java_library:junit",
   ]
 }
+
+android_java_prebuilt("exposed_instrumentation_api_publish_java") {
+  jar_path = "lib/exposed-instrumentation-api-publish-0.3-release-no-dep.jar"

[aluo, 2016/08/24 17:13:36]

I'm updating the exposed instrumentation api and runner to 0.5 version, see
https://codereview.chromium.org/2142413004.  Unless there's a specific reason to
use 0.3, you can omit this prebuilt and update the rules to 0.5 below after my
cl lands.  Please let me know so I can land 2142413004, thanks.

+}
+
+android_java_prebuilt("rules_java") {

[jbudorick, 2016/08/24 12:55:44]

Until you've got a complete runner jar, what's this expected to do? How will
this be used?

[the real yoland, 2016/08/24 19:04:18]

This is an example, basically, the Rules are, in a way, replacing TestCase to
provide activity context https://codereview.chromium.org/2266353003

[the real yoland, 2016/08/29 23:57:42]

Actually, just checked, there isn't a complete jar that merges runner.jar,
rules.jar and exposeda-instrumentation-api.jar together

+  jar_path = "lib/rules-0.3-release-no-dep.jar"
+}