| commit | 32794457fdcdcdca6f1f92579be76723e7a2601c | [log] [tgz] |
|---|---|---|
| author | Yigit Boyar <yboyar@gmail.com> | Tue Oct 31 19:54:24 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Oct 31 19:55:38 2023 -0700 |
| tree | a6147ceb6f3b7849e44065ed2e647751ba73fc71 | |
| parent | 14f0ecedc6eb0beba5fad91c719e0c7f57c3ce77 [diff] |
[GH] Move playground projects into a separate folder This PR updates the GitHub setup to position playground projects outside the main project structure. This is done for 2 reasons: * Running `gw` (gradle shortcut that finds the closest gradlew) would match the playground gradlew even when the developer is not using playground * Android studio would pick the playground settings.gradle file when running jvm tests from studio's gutter icon. This caused a lot of confusion for developers as it might run with different dependencies, confuse studio etc. This updates moves them into playground-projects folder, also names each one as `projectName-playground` to further avoid any confusion with the parent project (e.g. :room gets included automatically when :room-common is included, we don't want it to conflict with the playground root project). I updated the workflow files to use the new setup (PR will fail on target since it will use the old workflow file) I've also added an empty playground project to run ktlint on CI so that it doesn't get affected by other projects. Bug: n/a Test: CI This is an imported pull request from https://github.com/androidx/androidx/pull/624. Resolves #624 Github-Pr-Head-Sha: ebfcbba1a0fa94306eb6fb4803097dc527554e3d GitOrigin-RevId: c1db28e996eabad2396ee431c6e95afef234ca22 Change-Id: I6c2176678187dc5f043cdb4391496ee372834c7f
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.