Gitiles
Code Review Sign In
review.blissroms.org / platform_frameworks_support / 4e29091e542d87269447fdc8b3254ce86af06845
commit4e29091e542d87269447fdc8b3254ce86af06845[log] [tgz]
authorFilip Pavlis <pavlis@google.com>Wed May 02 14:50:27 2018 +0100
committerFilip Pavlis <pavlis@google.com>Wed May 02 19:59:36 2018 +0100
treecd0c451e0f9a308671c27481252a7ed84845c278
parent128cfb26218a787fd14df2b396d1e90b3f58093b [diff]
Relax conditions for jetifier xml rewrite.

Jetifier had very restricted set of XML tags to rewrite. This was
causing failures and the list had to be extened. Because this does not
scale well I have relaxed the selectors and jetifier now tries to
rewrite basically anything in quotes or in tags.

Another tiny change is that Jetifier will move files no matter if it is
rewriting support library or not. This is related to the new strategy
that we will rewrite files that are not originally from SL but are in
the same namespace and satisfy our rules. By this we won't break usages
of internal APIs.

Test: Added
Change-Id: I20041897eaa98899294092bd88a9371d811026d6
Fix: 79111795
Bug: 64833662
13 files changed
tree: cd0c451e0f9a308671c27481252a7ed84845c278
  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. core/
  15. cursoradapter/
  16. customview/
  17. development/
  18. documentfile/
  19. drawerlayout/
  20. dynamic-animation/
  21. emoji/
  22. exifinterface/
  23. fragment/
  24. frameworks/
  25. gradle/
  26. graphics/
  27. gridlayout/
  28. heifwriter/
  29. interpolator/
  30. jetifier/
  31. leanback/
  32. leanback-preference/
  33. legacy/
  34. lifecycle/
  35. loader/
  36. localbroadcastmanager/
  37. media/
  38. media-widget/
  39. mediarouter/
  40. navigation/
  41. paging/
  42. palette/
  43. percent/
  44. persistence/
  45. preference/
  46. print/
  47. recommendation/
  48. recyclerview-selection/
  49. room/
  50. samples/
  51. scripts/
  52. slices/
  53. slidingpanelayout/
  54. swiperefreshlayout/
  55. testutils/
  56. testutils-ktx/
  57. textclassifier/
  58. transition/
  59. tv-provider/
  60. v7/
  61. viewpager/
  62. viewpager2/
  63. wear/
  64. webkit/
  65. webkit-codegen/
  66. work/
  67. .gitignore
  68. adding-support-library-as-included-build.md
  69. build.gradle
  70. gradle.properties
  71. gradlew
  72. include-composite-deps.gradle
  73. include-support-library.gradle
  74. LICENSE.txt
  75. OWNERS
  76. PREUPLOAD.cfg
  77. README.md
  78. 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)