commit | 881d7830d2ee1018c2b7be923a17fcae1f834c55 | [log] [tgz] |
---|---|---|
author | Chuck Jazdzewski | Mon Apr 22 16:14:45 2024 -0700 |
committer | Chuck Jazdzewski | Thu Apr 25 10:31:47 2024 -0700 |
tree | 5d48d84f44085ef67ec7b7825d2ef13fae6738ba | |
parent | 202631e30455b712dd5ec9ed638e7c69b0d85a49 [diff] |
Change how compiler features are rolled out This change introduces a new mechnism to roll out compiler features that are intended to be made the eventual default behavior. Instead of introducing a flag that can be confused with configuration option will always be options, all such features are now enabled or disabled through "featureFlag". Relnote: """Changed how features being rolled out are enabled and disabled. Features, such as strong skipping and non-skipping group optimizations are now enabled through the "featureFlag" option instead of their own option. A feature with a feature flag start off initially disabled and will eventually become enabled by default. For example, to enable strong skipping use: -P plugin:androidx.compose.compiler.plugins.kotlin:featureFlag=StrongSkipping To enable the non-skipping groups optimization use: -P plugin:androidx.compose.compiler.plugins.kotlin:featureFlag=OptimizeNonSkippingGroups the options strongSkipping, experimentialStrongSkipping, and nonSkippingGroupOptimization are now all depricated and will report an warning if used but are still honored. A feature flag can be removed if its name is prefixed with a "-". For example: -P plugin:androidx.compose.compiler.plugins.kotlin:featureFlag=-StrongSkipping will disable strong skipping. Using a feature that is unknown to the plugin will report a warning. If a feature is enabled that is enabled by default or disabled and is disabled by default, a warning will be issued. """ Test: ./gradlew :compose:c:c-h:i-t:check Change-Id: Iab20b3f0e5e818a98f7952bbe1e1ebbd2b8251c7
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.