| commit | 59696291a44154f3682f1261afc59f00806b4fb3 | [log] [tgz] |
|---|---|---|
| author | Googler <yuyueny@google.com> | Tue Dec 26 14:31:53 2023 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Dec 26 14:33:24 2023 -0800 |
| tree | a424064c13fc52c8595231e95595c77717da5ae6 | |
| parent | d9dc4fde4c8d06498f39b54a81d4e7fa1e5b5b30 [diff] |
Move `InvalidGlobPatternException` and `GlobException` into two separate Java files In the follow up change, these two exceptions are expected to have new clients: * The new `GlobsValue#GlobRequest` checks whether glob pattern is valid and possibly throw `InvalidGlobPatternException`. * The new `GlobsFunction` also wraps and re-throws `InconsistentFilesystemException` and `FileSymlinkInfiniteExpansionException` discovered by the `StateMachine`. This is similar to the existing logic in `GlobFunctionWithRecursionInSingleFunction`. So I want to move both classes into separate files so that they can be shared. PiperOrigin-RevId: 593857554 Change-Id: I30499d5e70253048eb682f6d8878b6ec90798f81
{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
