commit | beaf451227ca8ddd1b9329186b5029c7091ecaf5 | [log] [tgz] |
---|---|---|
author | Filip Pavlis <pavlis@google.com> | Wed Oct 11 18:10:29 2017 +0100 |
committer | Filip Pavlis <pavlis@google.com> | Tue Nov 21 18:24:02 2017 +0000 |
tree | 769abf2c0407c7701ce80a33086fa2174eae68dc | |
parent | 9f29f4a040c61cdbc2bbb5adb9c90fd5691cac57 [diff] |
Add preprocessor to jetifier to generate types map The rewrite rules we have been using until now are easy to write but at the end we will need a map of every single change that happened in the support library due to the refactoring. Because of that I'm introducing a preprocessor tool that will firstly run all the rules over the real support libraries to build the complete map. This map is then added to a newly generated config. This generated config will be shipped with jetifier. The libraries bytecode and XML resources rewriting was updated to use the generated types map instead of the rules itself. That makes it simpler and also prevents rewriting of anything that is not expected to be rewritten. The tool has also few new extra checks. If the preprocessor will find any java type from support library that is not covered by any of the given rules it will fail. That will ensure that our mapping is not missing anything. Also the jetifier itself will fail if it finds a type that is supposed to be rewritten but there is no rule in the map. This will allow us to detect that we are rewriting older versions of support libraries for instance. Bug: b/64833662 Test: MapGenerationTest Change-Id: I5d326717b5c224cad363835d2c65eb2673e4927e
We are not currently accepting new modules, features, or behavior changes.
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
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
.
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
Run FooBarTest
Run android.support.foobar
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.
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)?