commit | 26940688554febd7996436faaccecf21336990e2 | [log] [tgz] |
---|---|---|
author | Louis Pullen-Freilich <lpf@google.com> | Wed May 01 16:44:01 2019 +0100 |
committer | Louis Pullen-Freilich <lpf@google.com> | Wed May 01 19:01:02 2019 +0100 |
tree | cf446d261f0a24ed7aee7b36d419085b2cfd2796 | |
parent | 5e94150beab6d3ac7109b4d4ab578974a39f23c8 [diff] |
Cleans up issues across a few modules Enables warnings on ui-text, ui-test, ...:ui-material-studies, ...:ui-material-demos and fixes issues that break as a result Fixes every @Children usage to properly specify @Composable, this is needed to prevent compiler warnings. Fixes some incorrect package names in text/src/androidTest Also renames ui-material-studies folder to material-studies to match material-demos Bug: b/131745428 Bug: b/130787808 Test: ./gradlew compileDebugKotlin && ./gradlew compileDebugAndroidTestKotlin Change-Id: Ib70af30acde7440afb59130e0dddb5a463516cbe
We are not currently accepting new modules.
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 androidx-master-dev
The first time you initialize the repository, it will ask for user name and email.
Now your repository is set to pull only what you need for building and running AndroidX libraries. Download the code (and grab a coffee while we pull down 3GB):
repo sync -j8 -c
You will use this command to sync your checkout in the future - it’s similar to git fetch
To open the project with the specific version of Android Studio recommended for developing:
cd path/to/checkout/frameworks/support/ ./studiow
and accept the license agreement when prompted. 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 AndroidX library from command line:
cd path/to/checkout/frameworks/support/ ./gradlew createArchive
You can build maven artifacts locally, and test them directly in your app:
./gradlew createArchive
And put in your project build.gradle
file:
handler.maven { url '/path/to/checkout/out/support/build/support_repo/' }
Run FooBarTest
Run androidx.foobar
The AndroidX repository has a set of Android applications that exercise AndroidX 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 either <libraryname>-integration-tests-testapp
, or support-\*-demos
(e.g. support-4v-demos
or support-leanback-demos
). You can run them by clicking Run > Run ...
and choosing the desired application.
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
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)?
If the upload succeeds, you'll see output like:
remote: remote: New Changes: remote: https://android-review.googlesource.com/c/platform/frameworks/support/+/720062 Further README updates remote:
To edit your change, use git commit --amend
, and re-upload.
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()
, jcenter()
, or mavenCentral()
. We store copies of these dependencies to have hermetic builds. You can pull in a new dependency using our importMaven tool.