jlengrand/moderne-docs
1
0
Fork 0
mirror of https://github.com/jlengrand/moderne-docs.git synced 2026-03-10 08:31:21 +00:00
Code Issues Packages Projects Releases Wiki Activity

remove link to hidden bazel doc

Browse Source
This commit is contained in:
Mike Solomon
2025-01-15 08:10:36 -08:00
parent fde0f2dce0
commit 3388a6ca1a
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/user-documentation/moderne-cli/how-to-guides/build-steps.md
View File

@@ -10,7 +10,7 @@ In the default configuration, the CLI first looks for Maven build files, then Gr
The CLI supports 3 external build step types and a resource build step.
The external build step types are Maven, Gradle, and [Bazel](./bazel-support.md). For each of these steps, the CLI will do a file walk from the root directory of a repository looking for top level build files of that type. The execution of that step will execute each top level build file.
The external build step types are Maven, Gradle, and Bazel. For each of these steps, the CLI will do a file walk from the root directory of a repository looking for top level build files of that type. The execution of that step will execute each top level build file.
### External build tool steps
@@ -69,7 +69,7 @@ build:
**/*
```
The order of the steps is important, as any file parsed by one step will be skipped by a subsequent step. In this way, the steps drive the order of precedence of build tools. 
The order of the steps is important, as any file parsed by one step will be skipped by a subsequent step. In this way, the steps drive the order of precedence of build tools.
:::danger
Be careful if you remove a build step type as that will make it so that build type will never be used. For instance, if you removed the `bazel` build step, Bazel will never be used to build any files -- even if there were Bazel files present. Instead, Bazel files would be parsed with the `resource` parser.