Fix //src:bazel-dev misplacing the embedded JDK (https://github.com/bazelbuild/bazel/pull/28841) ### Description Fixes a bug where the `//src:bazel-dev` target doesn't have the JDK at the correct location in the generated archive, causing the launcher to fall back to system java instead. #### Before (note I don't have `java` installed) ``` $ bazel build //src:bazel-dev $ bazel-bin/src/bazel-dev FATAL: Could not find system javabase. Ensure JAVA_HOME is set, or javac is on your PATH. ``` #### After ``` $ bazel build //src:bazel-dev $ bazel-bin/src/bazel-dev Starting local Bazel server (no_version) and connecting to it... [bazel development version] Usage: bazel <command> <options> ... Available commands: aquery Analyzes the given targets and queries the action graph. build Builds the specified targets. ... ``` ### Motivation Bug fix ### Build API Changes No ### Checklist - [ ] I have added tests for the new use cases (if any). - [ ] I have updated the documentation (if applicable). ### Release Notes RELNOTES: None Closes #28841. PiperOrigin-RevId: 877776855 Change-Id: I5fdb2de0f557292938ec327ea4ff353826a64fdc
{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.
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
