Google Git
Sign in
android / platform / frameworks / support / 055787fc6f88468aa36a8c20938c1e9ae4863cc4
commit055787fc6f88468aa36a8c20938c1e9ae4863cc4[log] [tgz]
authoromarismail <[email protected]>Thu Feb 22 23:32:44 2024 +0000
committerOmar Ismail <[email protected]>Mon Apr 08 16:13:02 2024 -0400
tree76f278f756d5dc9946e4df607cb8158c17e670fd
parent9180962e964f15ec8721e0b22836e6d3870a320e [diff]
Repackage Wear projects that use protobufs into multiple JARs

We extract out the repackaged Google Protobuf dependency into a separate
project. We also repackage classes with any references to Google Protobuf
updated to refer to the new package

After this change, the protolayout-proto library's pom file will have a
new dependeny adde to it: protolayout-external-protobuf

BUG: 296864329

TESTED: bumped up version of tiles and protolayout and then published
locally. I bumped the version so that I guarantee Gradle always fetches
the local version. Then, I created a new Android project with a pointer
to the local Maven repo.

In the app buil file, I added

  implementation("androidx.wear.tiles:tiles-proto:1.4.0-alpha02")

as a dependency and synced. I saw the tiles-proto get downloaded, as
well as protolayout-proto and protolayout-external-protobuf. Confimed as
well by running ./gradlew :app:dependencies , which showed all these
artifacts being brought in, as well as the dependency constraint between
tiles-proto and protolayout-proto.

In the app MainActivity.kt, I then added a simple print statement:

    println(Tile.newBuilder().build())

compiled and ran the app on the phone and it succeeded.

Change-Id: Ie7618afa685e23332a1d64a67f73a93519247e8d
30 files changed
tree: 76f278f756d5dc9946e4df607cb8158c17e670fd
  1. .github/
  2. .idea/
  3. activity/
  4. annotation/
  5. appactions/
  6. appcompat/
  7. appintegration/
  8. appsearch/
  9. arch/
  10. asynclayoutinflater/
  11. autofill/
  12. benchmark/
  13. biometric/
  14. bluetooth/
  15. browser/
  16. buildSrc/
  17. buildSrc-tests/
  18. busytown/
  19. camera/
  20. car/
  21. cardview/
  22. collection/
  23. compose/
  24. concurrent/
  25. constraintlayout/
  26. contentpager/
  27. coordinatorlayout/
  28. core/
  29. credentials/
  30. cursoradapter/
  31. customview/
  32. datastore/
  33. development/
  34. docs/
  35. docs-public/
  36. docs-tip-of-tree/
  37. documentfile/
  38. draganddrop/
  39. drawerlayout/
  40. dynamicanimation/
  41. emoji/
  42. emoji2/
  43. enterprise/
  44. exifinterface/
  45. external/
  46. fragment/
  47. glance/
  48. gradle/
  49. graphics/
  50. gridlayout/
  51. health/
  52. heifwriter/
  53. hilt/
  54. input/
  55. inspection/
  56. interpolator/
  57. javascriptengine/
  58. kruth/
  59. leanback/
  60. lifecycle/
  61. lint/
  62. lint-checks/
  63. loader/
  64. media/
  65. mediarouter/
  66. metrics/
  67. navigation/
  68. paging/
  69. palette/
  70. pdf/
  71. percentlayout/
  72. placeholder/
  73. placeholder-tests/
  74. playground-common/
  75. playground-projects/
  76. preference/
  77. print/
  78. privacysandbox/
  79. profileinstaller/
  80. recommendation/
  81. recyclerview/
  82. remotecallback/
  83. resourceinspection/
  84. room/
  85. safeparcel/
  86. samples/
  87. savedstate/
  88. security/
  89. sharetarget/
  90. slice/
  91. slidingpanelayout/
  92. sqlite/
  93. stableaidl/
  94. startup/
  95. swiperefreshlayout/
  96. test/
  97. testutils/
  98. text/
  99. tracing/
  100. transition/
  101. tv/
  102. tvprovider/
  103. vectordrawable/
  104. versionedparcelable/
  105. viewpager/
  106. viewpager2/
  107. wear/
  108. webkit/
  109. window/
  110. work/
  111. .gitignore
  112. build.gradle
  113. cleanBuild.sh
  114. code-review.md
  115. CONTRIBUTING.md
  116. gradle.properties
  117. gradlew
  118. libraryversions.toml
  119. LICENSE.txt
  120. OWNERS
  121. PREUPLOAD.cfg
  122. README.md
  123. settings.gradle
  124. studiow
  125. TEXT_OWNERS
README.md

Android Jetpack

Revved up by Develocity

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.

Contribution Guide

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:

Code Review Etiquette

When contributing to Jetpack, follow the code review etiquette.

Accepted Types of Contributions

  • Bug fixes - needs a corresponding bug report in the Android Issue Tracker
  • Each bug fix is expected to come with tests
  • Fixing spelling errors
  • Updating documentation
  • Adding new tests to the area that is not currently covered by tests
  • New features to existing libraries if the feature request bug has been approved by an AndroidX team member.

We are not currently accepting new modules.

Checking Out the Code

Head over to the onboarding docs to learn more about getting set up and the development workflow!

Continuous integration

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.

Password and Contributor Agreement before making a change

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

Getting reviewed

  • After you run repo upload, open r.android.com
  • Sign in into your account (or create one if you do not have one yet)
  • Add an appropriate reviewer (use git log to find who did most modifications on the file you are fixing or check the OWNERS file in the project's directory)

Handling binary dependencies

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.