| commit | ff6c0333e4f957bb9f7ab5401b01dbf3e9b515b1 | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Fri Apr 01 09:12:52 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Apr 01 09:14:21 2022 -0700 |
| tree | 3a4b451326d8b175f90f2d513bcef9ecc2320684 | |
| parent | 8bd64541ab283a4e3f4c3b97e7df49fb06da4e60 [diff] |
Fixes for native/starlark differences for java_lite_proto_library I've added a new private parameter create_output_source_jar inside java_common which does not create a new action for output_source_jar since it's already created in JavaInfoBuildHelper (it’s the same as source_jar). I’ve also added a test for the new parameter. Added output_source_jar in java_common.compile which is used as a source_jar for java_lite_proto_library rule. I’ve removed adding runtimes from exports inside JavaInfo.merge since we don’t need it (it’s enough to have runtimes from providers). I've removed jplCorrectlyDefinesDirectJars_strictDepsEnabled test from Starlark test since it's a duplication from JavaLiteProtoLibraryTest. I've also just updated the original test with assertion of source files. I've also added proto javacopts to the aspect by exporting relevant JavaToolchain function to Starlark in order to resolve IllegalAccessError failing tests. Tested it since it must be private API for now. Right now testing javacopts is needed - I've stoped ignoring them inside StarlarkJavaLiteProtoLibraryTest. PiperOrigin-RevId: 438838680
{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
