Perform the resource name obfuscation optimization based on presence of ProGuard specs, rather than `-c opt`. Includes a bit of refactoring around how we determine whether resource shrinking is to be performed. Rather than checking for the presence of ProGuard specs deep down within shrinkResources(), instead check at a higher level where the code can be incorporated with other condition logic, such as in AndroidDataContext.useResourceNameObfuscation() PiperOrigin-RevId: 271412430
{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:
See CONTRIBUTING.md
Bazel is released in ‘Beta’. See the product roadmap to learn about the path toward a stable 1.0 release.