Use an aar to define bridge dependency (#3892)

This commit is contained in:
Andrew Haisting 2024-09-10 11:33:49 -05:00 committed by GitHub
parent 8489693d84
commit b94a1adda9
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
5 changed files with 21 additions and 2 deletions

View file

@ -135,8 +135,8 @@ dependencies {
add("standardImplementation", dependencyNotation)
}
// TODO: this should use a versioned aar instead of referencing the project BITAU-94
implementation(project(":bridge"))
// TODO: this should use a versioned AAR instead of referencing a local AAR BITAU-94
implementation(files("libs/bridge-0.1.0-SNAPSHOT-release.aar"))
implementation(libs.androidx.activity.compose)
implementation(libs.androidx.appcompat)

Binary file not shown.

Binary file not shown.

View file

@ -3,6 +3,7 @@
## Contents
- [Compatibility](#compatibility)
- [Building](#building)
- [Versioning](#versioning)
- [Dependencies](#dependencies)
@ -16,6 +17,14 @@
- **Minimum SDK**: 28
- **Target SDK**: 34
## Building
To build an AAR for inclusion in consumer applications, run:
```sh
$ ./gradlew bridge:assembleRelease
```
## Versioning
This repository conforms to the following versioning convention:

View file

@ -40,6 +40,16 @@ android {
buildConfig = true
aidl = true
}
// Add version name to the output .aar file:
libraryVariants.all {
val variant = this
outputs
.map { it as com.android.build.gradle.internal.api.BaseVariantOutputImpl }
.forEach { output ->
val outputFileName = "bridge-${version}-SNAPSHOT-${variant.baseName}.aar"
output.outputFileName = outputFileName
}
}
}
kotlin {