commit | ef1265ecca338a7bb3929def8085236d45ace500 | [log] [tgz] |
---|---|---|
author | Daniel Santiago Rivera <danysantiago@google.com> | Thu Jun 29 11:16:59 2023 -0400 |
committer | Daniel Santiago Rivera <danysantiago@google.com> | Thu Jun 29 16:29:27 2023 -0400 |
tree | 05e9026558ee68e9b2c5f4148d0ddb3d51cf5887 | |
parent | c3f15cb7014aef81f2161035602782a65e0b569b [diff] |
Update Room Gradle plugin APIs to not always require per-variant configurations. Most Room users don't have per-variant schemas which means having per-variant schema directories can decrease the user experience, specially as users migrate from the current annotation processor option approach to the plugin as per-variant directories where also not needed then if not necessary. This change updates the plugin APIs to accept a global location for all variants without creating multiple directories, enabling smoother migrations but also flexible enough to configure flavors or build type schemas while still retaining the benefits of the plugin (reproducible and cacheable builds). The API is updated to contain overloads for configuring a single schema location or per-variant locations: ``` room { // For all variants schemaLocation("$projectDir/schemas/") // For a specific variant schemaLocation("variantName", ("$projectDir/schemas/variantName") } ``` and an example usage assuming two build flavors: ‘demo’ and ‘full’ and the two default build types ‘debug’ and ‘release’: ``` room { // Applies to demoDebug only schemaLocation("demoDebug", ("$projectDir/schemas/demoDebug") // Applies to demoDebug and demoRelease schemaLocation("demo", ("$projectDir/schemas/demo") // Applies to demoDebug and fullDebug schemaLocation("debug", ("$projectDir/schemas/debug") } ``` Bug: 278266663 Test: RoomGradlePluginTest Change-Id: I09d6f9a77d3737bef2ce73193344a8b31f5059a8
Jetpack is a suite of libraries, tools, and guidance to help developers write high-quality apps easier. These components help you follow best practices, free you from writing boilerplate code, and simplify complex tasks, so you can focus on the code you care about.
Jetpack comprises the androidx.*
package libraries, unbundled from the platform APIs. This means that it offers backward compatibility and is updated more frequently than the Android platform, making sure you always have access to the latest and greatest versions of the Jetpack components.
Our official AARs and JARs binaries are distributed through Google Maven.
You can learn more about using it from Android Jetpack landing page.
For contributions via GitHub, see the GitHub Contribution Guide.
Note: The contributions workflow via GitHub is currently experimental - only contributions to the following projects are being accepted at this time:
When contributing to Jetpack, follow the code review etiquette.
We are not currently accepting new modules.
Head over to the onboarding docs to learn more about getting set up and the development workflow!
Our continuous integration system builds all in progress (and potentially unstable) libraries as new changes are merged. You can manually download these AARs and JARs for your experimentation.
Before uploading your first contribution, you will need setup a password and agree to the contribution agreement:
Generate a HTTPS password: https://android-review.googlesource.com/new-password
Agree to the Google Contributor Licenses Agreement: https://android-review.googlesource.com/settings/new-agreement
AndroidX uses git to store all the binary Gradle dependencies. They are stored in prebuilts/androidx/internal
and prebuilts/androidx/external
directories in your checkout. All the dependencies in these directories are also available from google()
, or mavenCentral()
. We store copies of these dependencies to have hermetic builds. You can pull in a new dependency using our importMaven tool.