commit | 0a7dc89e9df7d6caf0556369449d1bab6e69a553 | [log] [tgz] |
---|---|---|
author | Jeff Gaston <jeffrygaston@google.com> | Fri Aug 25 11:09:16 2023 -0400 |
committer | Jeff Gaston <jeffrygaston@google.com> | Fri Aug 25 13:38:42 2023 -0400 |
tree | 6e9572c1bf190d1e21d7a315d629e6fa959cb389 | |
parent | 96167c5f68f9c298fad9ace77f7d7d206bb2ed4b [diff] |
More robust fix for createProjectZip incorrectly reporting no inputs When Gradle runs a Zip/Copy task, Gradle appears to be caching the input directories and then not invalidating them if a subsequent task writes to those directories without declaring those writes. Previously we worked around this issue by ensuring that the specific triggering tasks executed in a certain order. This change implements a more robust fix that should apply to future occurrences of this problem in other projects too: it reduces the set of files that might be considered as inputs to the corresponding zip tasks, to exclude files from subprojects Bug: 295947829 Bug: https://github.com/gradle/gradle/issues/24368 Test: # zips still not missing if run in an unlucky order: echo 'afterEvaluate { project.tasks["createProjectZip"].mustRunAfter(":compose:material3:material3-adaptive:createProjectZip") project.tasks["compileReleaseKotlin"].mustRunAfter(":compose:material3:material3-adaptive:createProjectZip") } ' >> compose/material3/material3-adaptive/samples/build.gradle && rm ../../out/dist/repository/androidx/compose/material3 -rf && SNAPSHOT=true ./gradlew :compose:material3:material3-adaptive:verifyOutputscreateProjectZip :compose:material3:material3-adaptive:material3-adaptive-samples:verifyOutputscreateProjectZip --no-build-cache --rerun-tasks | cat Change-Id: I1c011d33a0016b3f012c789c2ee4028daaa2b27d
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.