| commit | 8bd989ed5fb0488922a9536233d167c3e37b765f | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Tue Feb 22 06:01:20 2022 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Feb 22 06:03:50 2022 -0800 |
| tree | edbc598ff3300fa6f91a81d9ddafb32f070ae3c0 | |
| parent | 2655ebe2f0bf13426b9b972f0a55101f95fdb533 [diff] |
Add android constraints inside java_lite_proto_library I’ve extended internal java semantics with add_constraints function (open source version doesn’t need it - empty function is enough). In order to use internal add_constraint in tests (which depends on java_common.add_contraints -> experimental only), I've added experimental_google_legacy_api build option to all tests which depends on android constraint and java_lite_proto_library. Resolved not allowed dependencies on .jar artifacts in Android binaries by adding JavaInfo inside 'provides' in java_lite_proto_library rule. I've also added java_lite_proto_aspect as an artifact name for JavaLiteProtoLibrary inside GoogleJavaSematics. PiperOrigin-RevId: 430192660
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
