Gitiles
Code Review Sign In
review.blissroms.org / platform_frameworks_support / 40e782170f16628bc2ca6eaf26e79289186f1005
commit40e782170f16628bc2ca6eaf26e79289186f1005[log] [tgz]
authorAurimas Liutikas <aurimas@google.com>Thu Jul 20 14:22:58 2017 -0700
committerAurimas Liutikas <aurimas@google.com>Fri Jul 21 12:21:33 2017 -0700
tree614e5c9374b600159494a5501473fbf6adc0fd7f
parentb47af90e730336e11bf744511f452e45bffe8bf4 [diff]
Fix the names of support library projects to match released names

Our internal names of projects did not match external project names:
eg. we used support-appcompat-v7 vs appcompat-v7. Renaming these to
correct names will fix top-of-tree-repo zip.

Bug: 63899246
Test: manually inspected ./gradlew buildOnServer
Change-Id: Ic44b115431060e465fa4d1d2076bb5f4843457f9
19 files changed
tree: 614e5c9374b600159494a5501473fbf6adc0fd7f
  1. .idea/
  2. annotations/
  3. api/
  4. app-toolkit/
  5. buildSrc/
  6. compat/
  7. core-ui/
  8. core-utils/
  9. customtabs/
  10. design/
  11. development/
  12. dynamic-animation/
  13. emoji/
  14. exifinterface/
  15. fragment/
  16. frameworks/
  17. gradle/
  18. graphics/
  19. lifecycle/
  20. media-compat/
  21. media-compat-test-client/
  22. media-compat-test-service/
  23. paging/
  24. percent/
  25. recommendation/
  26. room/
  27. samples/
  28. samples-flatfoot/
  29. scripts/
  30. testutils/
  31. transition/
  32. tv-provider/
  33. v13/
  34. v14/
  35. v17/
  36. v4/
  37. v7/
  38. wear/
  39. .gitignore
  40. Android.mk
  41. build.gradle
  42. CleanSpec.mk
  43. droiddoc.mk
  44. gradle.properties
  45. gradlew
  46. LICENSE.txt
  47. makeFlatfootRepo.sh
  48. pathmap.mk
  49. PREUPLOAD.cfg
  50. README.md
  51. 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.

Optional - Full Build

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

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)