You can define dependencies that in turn can define dependencies themselves.

In the end, a hierarchical tree of dependencies is built, and the **Dependency Injection** system takes care of solving all these dependencies for you (and their sub-dependencies) and providing (injecting) the results at each step.

     * Sets the project to resolve dependencies for.
     *
     * @param project The project to resolve dependencies for, may be {@code null}.
     * @return This request for chaining, never {@code null}.
     */
    DependencyResolutionRequest setMavenProject(MavenProject project);

    /**
     * Gets the filter used to exclude some dependencies from resolution.
     *

* All these *path operations* will have the list of `dependencies` evaluated/executed before them.
    * If you also declare dependencies in a specific *path operation*, **they will be executed too**.
    * The router dependencies are executed first, then the [`dependencies` in the decorator](dependencies/dependencies-in-path-operation-decorators.md){.internal-link target=_blank}, and then the normal parameter dependencies.

    - tutorial/body-updates.md
    - Dependencies:
      - tutorial/dependencies/index.md
      - tutorial/dependencies/classes-as-dependencies.md
      - tutorial/dependencies/sub-dependencies.md
      - tutorial/dependencies/dependencies-in-path-operation-decorators.md
      - tutorial/dependencies/global-dependencies.md
      - tutorial/dependencies/dependencies-with-yield.md
    - Security:

  dependencies:
    "@types/node" "*"

"@types/eslint-scope@^3.7.3":
  version "3.7.4"
  resolved "https://registry.yarnpkg.com/@types/eslint-scope/-/eslint-scope-3.7.4.tgz#37fc1223f0786c39627068a12e94d6e6fc61de16"
  integrity sha512-9K4zoImiZc3HlIp6AVUDE4CWYx22a+lhSZMYNpbjW04+YF0KWj4pJXnEMjdnFTiQibFFmElcsasJXDbdI/EPhA==
  dependencies:
    "@types/eslint" "*"
    "@types/estree" "*"

        assertEquals("b", pom.getValue("build/plugins[1]/dependencies[3]/artifactId"));
        assertEquals("1", pom.getValue("build/plugins[1]/dependencies[3]/version"));
        assertEquals("e", pom.getValue("build/plugins[1]/dependencies[4]/artifactId"));
        assertEquals("1", pom.getValue("build/plugins[1]/dependencies[4]/version"));
        assertEquals("d", pom.getValue("build/plugins[1]/dependencies[5]/artifactId"));

        Element root = doc.root();
        Element dependencies = root.child("dependencies").orElse(null);
        assertNotNull(dependencies, "dependencies should exist");
        Element dependency = dependencies.child("dependency").orElse(null);
        assertNotNull(dependency, "dependency should exist");

        // Insert elements in dependency according to dependency ordering

/**
 * Collects, flattens and resolves dependencies.
 */
@Experimental
public interface DependencyResolver extends Service {

    /**
     * Collects the transitive dependencies of some artifacts and builds a dependency graph for the given path scope.
     * Note that this operation is only concerned about determining the coordinates of the transitive dependencies and
     * does not actually resolve the artifact files.
     *

                }
            }
        }

        dependencies {
            if (!stage.runsIndependent && prevStage != null) {
                dependOnPreviousStageTrigger(model, prevStage, os)
            }

            snapshotDependencies(dependencies)
        }
    })

fun Dependencies.dependOnPreviousStageTrigger(
    model: CIBuildModel,
    prevStage: Stage,

* 所有的这些*路径操作*都将在自身之前计算/执行 `dependencies` 列表。
    * 如果你还在一个具体的*路径操作*中声明了依赖项，**它们也会被执行**。
    * 路由器的依赖项最先执行，然后是[装饰器中的 `dependencies`](dependencies/dependencies-in-path-operation-decorators.md){.internal-link target=_blank}，再然后是普通的参数依赖项。
    * 你还可以添加[具有 `scopes` 的 `Security` 依赖项](../advanced/security/oauth2-scopes.md){.internal-link target=_blank}。

/// tip

在 `APIRouter`中具有 `dependencies` 可以用来，例如，对一整组的*路径操作*要求身份认证。即使这些依赖项并没有分别添加到每个路径操作中。