Decouple events:events from Starlark eval and syntax. Split `Location` and `SyntaxError` into dedicated `location` and `syntax_error` build targets in `net/starlark/java/syntax` (re-exported by `:syntax`), and extract `PrintHandler` into a top-level `net.starlark.java.eval.PrintHandler` interface in its own `print_handler` build target in `net/starlark/java/eval` (re-exported by `:eval`). `PrintHandler` is decoupled from `StarlarkThread` via `PrintHandler.StarlarkThreadInfo`, which exposes `getCallerLocation()` and is implemented by `StarlarkThread`. `StarlarkThread.PrintHandler` is retained as a transitional subinterface while external callers migrate. Update `//src/main/java/com/google/devtools/build/lib/events:events` to depend only on `net/starlark/java/eval:print_handler`, `net/starlark/java/syntax:location`, and `net/starlark/java/syntax:syntax_error` instead of the full Starlark `eval` and `syntax` packages. PiperOrigin-RevId: 1013382020 Change-Id: Ibb816e348a3e90c6413f5e8c21c527264a8321ba
{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
