Gitiles
Code Review Sign In
review.blissroms.org / platform_frameworks_support / 39ac87e5407faa238681f3ddb65efc2e4c5144fe
commit39ac87e5407faa238681f3ddb65efc2e4c5144fe[log] [tgz]
authorFilip Pavlis <pavlis@google.com>Wed Apr 25 15:11:11 2018 +0100
committerFilip Pavlis <pavlis@google.com>Thu Apr 26 13:41:51 2018 +0000
tree72234055a5774d5da2330f1146834e487e185fca
parent7abf6308e79bc86d1a0ed5d560cf914d8cb4585d [diff]
Better versioning support in Jetifier.

Jetifier can now support versions as parameter which gives more
flexibility when rewriting depenndencies. The Processor will now use
latest available released versions of dependencies (which is alpha1 at
this moment). While standalone is using latest unreleased (1.0.0, 2.0.0)
but standalone can be given a version set via a new argument.

Bug: b/78541880
Bug: b/64833662
Test: Added
Change-Id: I03509e23fe3cb98f6e384b961ff9a009dd09199d
(cherry picked from commit 8fd78bd9fc36fa71b90ecd423de90c8f129f3709)
11 files changed
tree: 72234055a5774d5da2330f1146834e487e185fca
  1. .idea/
  2. annotations/
  3. api/
  4. app-toolkit/
  5. asynclayoutinflater/
  6. browser/
  7. buildSrc/
  8. car/
  9. cardview/
  10. collection/
  11. compat/
  12. content/
  13. coordinatorlayout/
  14. cursoradapter/
  15. customview/
  16. development/
  17. documentfile/
  18. drawerlayout/
  19. dynamic-animation/
  20. emoji/
  21. exifinterface/
  22. fragment/
  23. frameworks/
  24. gradle/
  25. graphics/
  26. gridlayout/
  27. heifwriter/
  28. interpolator/
  29. jetifier/
  30. leanback/
  31. leanback-preference/
  32. legacy/
  33. lifecycle/
  34. loader/
  35. localbroadcastmanager/
  36. media/
  37. media-widget/
  38. mediarouter/
  39. navigation/
  40. paging/
  41. palette/
  42. percent/
  43. persistence/
  44. preference/
  45. print/
  46. recommendation/
  47. recyclerview-selection/
  48. room/
  49. samples/
  50. scripts/
  51. slices/
  52. slidingpanelayout/
  53. swiperefreshlayout/
  54. testutils/
  55. textclassifier/
  56. transition/
  57. tv-provider/
  58. v7/
  59. viewpager/
  60. viewpager2/
  61. wear/
  62. webkit/
  63. webkit-codegen/
  64. work/
  65. .gitignore
  66. adding-support-library-as-included-build.md
  67. build.gradle
  68. gradle.properties
  69. gradlew
  70. include-composite-deps.gradle
  71. include-support-library.gradle
  72. LICENSE.txt
  73. OWNERS
  74. PREUPLOAD.cfg
  75. README.md
  76. settings.gradle
README.md

AOSP Support Library Contribution Guide

Accepted Types of Contributions

  • Bug fixes (needs a corresponding bug report in b.android.com)
  • 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

We are not currently accepting new modules, features, or behavior changes.

Checking Out the Code

NOTE: You will need to use Linux or Mac OS. Building under Windows is not currently supported.

Follow the “Downloading the Source” guide to install and set up repo tool, but instead of running the listed repo commands to initialize the repository, run the folowing:

repo init -u https://android.googlesource.com/platform/manifest -b ub-supportlib-master

Now your repository is set to pull only what you need for building and running support library. Download the code (and grab a coffee while we pull down 7GB):

repo sync -j8 -c

You will use this command to sync your checkout in the future - it’s similar to git fetch

Using Android Studio

Open path/to/checkout/frameworks/support/ in Android Studio. Now you're ready edit, run, and test!

If you get “Unregistered VCS root detected” click “Add root” to enable git integration for Android Studio.

If you see any warnings (red underlines) run Build > Clean Project.

Builds

Full Build (Optional)

You can do most of your work from Android Studio, however you can also build the full support library from command line:

cd path/to/checkout/frameworks/support/
./gradlew createArchive

Building Support Library as part of your App build

If you intend to repeatedly make changes to Support Library and to wish to see the results in your app, and you don't want to have to repeatedly build them as separate Gradle projects, you can configure your app build to build Support Library too

Running Tests

Single Test Class or Method

  1. Open the desired test file in Android Studio.
  2. Right-click on a test class or @Test method name and select Run FooBarTest

Full Test Package

  1. In the project side panel open the desired module.
  2. Find the directory with the tests
  3. Right-click on the directory and select Run android.support.foobar

Running Sample Apps

Support library has a set of Android applications that exercise support library code. These applications can be useful when you want to debug a real running application, or reproduce a problem interactively, before writing test code.

These applications are named support-*-demos (e.g. support-4v-demos or support-leanback-demos. You can run them by clicking Run > Run ... and choosing the desired application.

Making a change

cd path/to/checkout/frameworks/support/
repo start my_branch_name .
(make needed modifications)
git commit -a
repo upload --current-branch .

If you see the following prompt, choose always:

Run hook scripts from https://android.googlesource.com/platform/manifest (yes/always/NO)?

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)