commit | 38f01c020fb8d7cac7bb25d27c5674365324bcf6 | [log] [tgz] |
---|---|---|
author | Zac Sweers <zsweers@slack-corp.com> | Sat Jan 25 03:22:24 2020 -0500 |
committer | android-build-prod (mdb) <android-build-team-robot@google.com> | Tue Mar 03 22:48:46 2020 +0000 |
tree | a0ecf252270c98989bc580c23206462bbc6a6380 | |
parent | d5498a88824e70f0c667b926faa115f557d4e47c [diff] |
Add missing `api` properties to IssueRegistries Without this, lint will actually mark these as lint issues (đ). Example case I discovered in my app due to ExperimentalIssueRegistry missing its definition ``` /home/runner/.gradle/caches/transforms-2/files-2.1/1622c9dbedd7af5f13d41d9ddee6db71/jetified-annotation-experimental-1.0.0/jars/lint.jar: Warning: Lint found an issue registry (androidx.annotation.experimental.lint.ExperimentalIssueRegistry) which did not specify the Lint API version it was compiled with. This means that the lint checks are likely not compatible. If you are the author of this lint check, make your lint IssueRegistry class contain override val api: Int = com.android.tools.lint.detector.api.CURRENT_API or from Java, @Override public int getApi() { return com.android.tools.lint.detector.api.ApiKt.CURRENT_API; } If you are just using lint checks from a third party library you have no control over, you can disable these lint checks (if they misbehave) like this: android { lintOptions { disable "UnsafeExperimentalUsageError", "UnsafeExperimentalUsageWarning" } } [ObsoleteLintCustomCheck] ``` Test: Pending CR request for one, as none others test this Fixes: b/150699401 Change-Id: Id3824764ea6d93b170187c57e01a4a1eda378ec2 (cherry picked from commit 8cd20b246db465fb0a0acabfdf4e255f46fac404)
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.
When contributing to Jetpack, follow the code review etiquette.
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 "you@example.com"
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 the following at the top of your ârepositoriesâ property in your project build.gradle
file:
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.