Move nearby apex to tethering
Nearby will be merged together with the tethering/connectivity APEX, so
that module maintenance efforts can be reduced, and the two codebases
can evolve the interfaces that they expose to each other over time.
Bug: 189355156
Test: m
Change-Id: I7c34466a850cb437171ea15367a24f84305bd3f7
diff --git a/nearby/halfsheet/Android.bp b/nearby/halfsheet/Android.bp
index 82d0933..3f4f258 100644
--- a/nearby/halfsheet/Android.bp
+++ b/nearby/halfsheet/Android.bp
@@ -20,14 +20,15 @@
name: "HalfSheetDefaults",
srcs: ["src/**/*.java"],
sdk_version: "module_current",
- min_sdk_version: "current",
+ // This is included in tethering apex, which uses min SDK 30
+ min_sdk_version: "30",
target_sdk_version: "current",
manifest: "AndroidManifest.xml",
plugins: ["java_api_finder"],
jarjar_rules: ":nearby-jarjar-rules",
libs: [
"framework-bluetooth",
- "framework-nearby-pre-jarjar",
+ "framework-connectivity-tiramisu",
"nearby-service-string",
],
static_libs: [
@@ -49,7 +50,7 @@
static_libs: [
"com.google.android.material_material",
],
- apex_available: ["com.android.nearby",],
+ apex_available: ["com.android.tethering",],
}
android_app_certificate {