commit | d7f85f6a42bebbc35e50e57cfae9b70373aead9d | [log] [tgz] |
---|---|---|
author | Jeff Gaston <[email protected]> | Wed Jul 17 18:26:48 2019 -0400 |
committer | Jeff Gaston <[email protected]> | Wed Jul 24 10:21:36 2019 -0400 |
tree | e858a1fd882267f5f1dd40d7d44434b1e1cbd109 | |
parent | 7f05e3721db86e6fb277b86356f28f4f7f8aa2cf [diff] |
Having checkApiRelease validate current.txt against ${prev.txt} rather than validating the source code against ${prev.txt} This way checkApiRelease doesn't need to worry about redoing the same filtering as generateApi Also, this change modifies a few api files to make checkApi pass again (Metalava catches a slightly different set of errors when checking against txt files) Some nullability annotations in lifecycle/ seem to have been missed when I updated metalava in 6edd4a4d49f41d00f29588462388e5b179a9bb98 androidx.recyclerview.selection.SelectionTracker had its restriction scope changed in 0c2a7091f663f8e853290ecb2a84c08fc7adac86 , which says it was never called from another library In slices/core/api, even after these additions, the file restricted_1.1.0-alpha02.ignore still only contains one additional exemption that restricted_1.1.0-alpha01.ignore doesn't have, which is AddedAbstractMethod: androidx.slice.SliceManager#getPinnedSpecs(android.net.Uri) , but this method wasn't truly added, just reannotated in 237c8946756af4b0fe9d0fa3965593e247d53698 Test: ./gradlew checkApi Test: sed -i "s/onMenuItemClick/onMenuItemClick2/g" appcompat/api/1.1.0-rc01.txt && ./gradlew :appcompat:checkApiRelease # and notice that checkApiRelease fails Test: sed -i "s/setTag/setTag2/g" coordinatorlayout/api/restricted_1.1.0-beta01.txt && ./gradlew :coordinatorlayout:checkApiRelease # and notice that checkApiRelease fails Test: find coordinatorlayout/ -name "*.java" | xargs sed 's/getBehavior/getBehavior2/g' -i && ./gradlew :coordinatorlayout:checkApiRelease # and notice that checkApiRelease still fails even without having run updateApi yet Bug: 135951300 Change-Id: I4599e298a32b834800105a1149d08a56f9abb659
Jetpack is a suite of libraries, tools, and guidance to help developers write high-quality apps easier. These components help you follow best practices, free you from writing boilerplate code, and simplify complex tasks, so you can focus on the code you care about.
Jetpack comprises the androidx.*
package libraries, unbundled from the platform APIs. This means that it offers backward compatibility and is updated more frequently than the Android platform, making sure you always have access to the latest and greatest versions of the Jetpack components.
Our official AARs and JARs binaries are distributed through Google Maven.
You can learn more about using it from Android Jetpack landing page.
We are not currently accepting new modules.
NOTE: You will need to use Linux or Mac OS. Building under Windows is not currently supported.
repo
(Repo is a tool that makes it easier to work with Git in the context of Android. For more information about Repo, see the Repo Command Reference)mkdir ~/bin PATH=~/bin:$PATH curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo chmod a+x ~/bin/repo
git config --global user.name "Your Name" git config --global user.email "[email protected]"
mkdir androidx-master-dev cd androidx-master-dev
repo
command to initialize the repository.repo init -u https://android.googlesource.com/platform/manifest -b androidx-master-dev
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/androidx/build/support_repo/' }
Our continuous integration system builds all in progress (and potentially unstable) libraries as new changes are merged. You can manually download these AARs and JARs for your experimentation.
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.