| commit | 8b7f1ee164e1479d41b5cb24e4c6ed3334fd7e68 | [log] [tgz] |
|---|---|---|
| author | Jeff Gaston <[email protected]> | Thu Dec 08 14:26:54 2022 -0500 |
| committer | Jeff Gaston <[email protected]> | Thu Dec 08 14:41:48 2022 -0500 |
| tree | b645afa4988a7753d293d7b4af24cc2353ea155f | |
| parent | 7b177e4099de077e42b5bcab271a824e6286cb37 [diff] |
-XX:ReservedCodeCacheSize=576M
This is slightly higher than the amount of CodeCache space required by `./busytown/androidx.sh` according to 'jcmd ${GradleDaemonPid} Compiler.codecache'
Before this change, when I run `./busytown/androidx.sh`, `jcmd ${GradleDaemonPid} Compiler.codecache` tells me that the compilation cache was reset a bunch of times:
stopped_count=283, restarted_count=283
After this change, when I run `./busytown/androidx.sh`, `jcmd ${GradleDaemonPid} Compiler.codecache` tells me that the compilation cache didn't need to be reset:
stopped_count=0, restarted_count=0
So, hopefully this will be an effective workaround for https://bugs.openjdk.org/browse/JDK-8295724 before we upgrade to a new version of Java.
Also, when I test this on my computer I find that this change reduces the time of the first Gradle run in busytown/androidx.sh from:
BUILD SUCCESSFUL in 36m 58s
to
BUILD SUCCESSFUL in 32m 24s
Bug: 260643754
Test: Treehugger runs busytown/*.sh
Change-Id: I36f4e0b350a95ecbb1b527160d40ce5a6a8ede8f
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(), jcenter(), or mavenCentral(). We store copies of these dependencies to have hermetic builds. You can pull in a new dependency using our importMaven tool.