commit | f119081cbb545ddfc6c144de0b5b3bcdd918a226 | [log] [tgz] |
---|---|---|
author | Jeff Gaston <jeffrygaston@google.com> | Tue Mar 26 17:15:42 2024 -0400 |
committer | Jeff Gaston <jeffrygaston@google.com> | Tue Mar 26 17:41:32 2024 -0400 |
tree | f3531e525d62d8c4c4b4a69ded4d2a921cdb9fde | |
parent | ede1f26c3ab35e44144f0a17468d9f4ecc01ce2a [diff] |
androidx_incremental deleting out/ at the start of the week To prevent the out/ dir from become very large Bug: 331445621 Test: Run `busytown/androidx_incremental.sh` and see that it creates a file `out/incremental/created_at.txt` and `out/incremental/updated_at.txt` that look like this: "Tue Mar 26 05:20:36 PM EDT 2024" Test: Modify out/incremental/created_at.txt to an earlier day in the week like: "Sun Mar 24 05:20:36 PM EDT 2024" and run `busytown/androidx_incremental.sh` again and see that it doesn't modify this file Test: Modify out/incremental/created_at.txt to specify a previous week like: "Sat Mar 23 05:20:36 PM EDT 2024" and run `busytown/androidx_incremental.sh` again and see: 1. androidx_incremental.sh prints that it's deleting the out/incremental dir 2. created_at.txt is updated to have a new time, like: Tue Mar 26 05:23:07 PM EDT 2024 Test: Run `echo corrupt > ../../out/incremental/created_at.txt` and ./busytown/androidx_incremental.sh` and see that it fails right away. Then run ./busytown/androidx_incremental.sh` and see that the second one doesn't fail with a date error (because the first one deleted the corrupted date) Change-Id: I105c7a5eac5c008977c2465a8ffc6f95426dd877
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.