commit | a13168a07a6545e9614541c28bf4ab19a2f6523e | [log] [tgz] |
---|---|---|
author | Chris Craik <[email protected]> | Thu Dec 12 09:48:11 2024 -0800 |
committer | Chris Craik <[email protected]> | Fri Dec 13 10:34:59 2024 -0800 |
tree | d69729478ba4a73c28ba79e7cbca7bdebdec41fd | |
parent | 098965d8cae2b18fe276e5b18856fb221d791226 [diff] |
Reland "Move PerfettoTraceProcessor -> TraceProcessor in benchmark-traceprocessor" Bug: 381134564 Bug: 382741383 Test: Tests in benchmark-macro Test: TraceProcessorBenchmark Test: ./gradlew :docs-tip-of-tree:docs Revert submission 3407319-revert-3376991-QEQTPRWJDK Reason for revert: dependent change aosp/3394905 was reverted, but has since relanded as aosp/3406159 Reverted changes: /q/submissionid:3407319-revert-3376991-QEQTPRWJDK Relnote: """Move PerfettoTraceProcessor to TraceProcessor in a new androidx.benchmark:benchmark-traceprocessor artifact, and make most of its API non-experimental. Any custom TraceMetric or anything reading from traces will need to update to the new TraceProcessor import. The new TraceProcessor API works exactly like the old one, but is a standalone interface library (somewhat analogous to the androidx.sql layer from Room) with an Android-specific implementation built into macrobenchmark. The new artifact can be used on JVM as well, but currently you'll need to start your own copy of the TraceProcessor binary and offer a port to connect to it on.""" This works around a crash in the docs build by moving package-info.java out of commonMain to both jvmMain/androidMain. Change-Id: I3a7675f25f4425745b6f255dcd1a0cec81a068ba
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.
For contributions via GitHub, see the GitHub Contribution Guide.
Note: The contributions workflow via GitHub is currently experimental - only contributions to the following projects are being accepted at this time:
When contributing to Jetpack, follow the code review etiquette.
We are not currently accepting new modules.
Head over to the onboarding docs to learn more about getting set up and the development workflow!
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.
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
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()
, or mavenCentral()
. We store copies of these dependencies to have hermetic builds. You can pull in a new dependency using our importMaven tool.