commit | e723c1f1f8e651ff6f05480eb93596ba31ceb39b | [log] [tgz] |
---|---|---|
author | Daniel Santiago Rivera <danysantiago@google.com> | Thu Apr 04 14:16:51 2024 -0400 |
committer | Daniel Santiago Rivera <danysantiago@google.com> | Tue Apr 16 14:27:03 2024 -0400 |
tree | a326a32516d18301d78ef683b5ab477ac6046393 | |
parent | accd5607e2d7974fadb3973598d5756d5e510329 [diff] |
Add a in-process and multi-process lock during database configuration. An exclusive lock that protects a region from concurrent in-process threads and other processes is used during first time database initialization, i.e. when the first database connection is opened and the database has to validate schema, maybe perform migrations or first time schema creation. Note that multi-process locking is only needed for file databases (not in memory) and only during that first time initialization. Also guard against recursive initialization and usage of the special name ':memory:' as a file database name. Bug: 316945717 Test: FileLockTest + BuilderTest Change-Id: Ic87280ce534ca235a4600cb059c6bac6147fccac
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.