assertViolations(result, 0, 2, 0);

        assertContains(
                result.getErrors().get(0), "'dependencies.dependency.version' for test:b:jar must be a valid version");
        assertContains(
                result.getErrors().get(1),
                "'dependencies.dependency.version' for test:c:jar must not contain any of these characters");
    }

    @Test

  </properties>

  <dependencyManagement>
    <dependencies>
      <dependency>
        <groupId>com.squareup.okhttp3</groupId>
        <artifactId>okhttp-bom</artifactId>
        <version>[5.2.0-SNAPSHOT,6.0.0-SNAPSHOT)</version>
        <type>pom</type>
        <scope>import</scope>
      </dependency>
    </dependencies>
  </dependencyManagement>

  <dependencies>
    <dependency>
      <groupId>junit</groupId>

Você pode definir dependências que por sua vez definem suas próprias dependências.

Por fim, uma árvore hierárquica de dependências é criada, e o sistema de **Injeção de Dependência** toma conta de resolver todas essas dependências (e as sub-dependências delas) para você, e provê (injeta) os resultados em cada passo.

  </scm>
  <dependencyManagement>
    <dependencies>
      <dependency>
        <groupId>maven-test</groupId>
        <artifactId>t05-b</artifactId>
        <version>1.0</version>
      </dependency>
      <dependency>
        <groupId>maven-test</groupId>
        <artifactId>t05-d</artifactId>
        <version>1.0</version>
      </dependency>
    </dependencies>
  </dependencyManagement>
  <dependencies>

      </dependency>
    </dependencies>
  </dependencyManagement>
  <dependencies>
    <dependency>
      <groupId>maven-test</groupId>
      <artifactId>t07-a</artifactId>
      <version>1.0</version>
    </dependency>
    <dependency>
      <groupId>maven-test</groupId>
      <artifactId>t07-c</artifactId>
      <version>1.0</version>
    </dependency>
  </dependencies>
  <build>
    <plugins>

        <version>1.0</version>
        <scope>test</scope>
        <optional>true</optional>
      </dependency>
    </dependencies>
  </dependencyManagement>
  <dependencies>
    <dependency>
      <groupId>maven-test</groupId>
      <artifactId>t08-a</artifactId>
      <version>1.0</version>
    </dependency>
    <dependency>
      <groupId>maven-test</groupId>
      <artifactId>t08-c</artifactId>

* これらすべての *path operations* では、実行前に `dependencies` のリストが評価・実行されます。
    * 特定の *path operation* に依存関係を宣言した場合は、**それらも実行されます**。
    * ルーターの依存関係が先に実行され、その後に[デコレータ内の `dependencies`](dependencies/dependencies-in-path-operation-decorators.md)、次に通常のパラメータ依存関係が続きます。
    * [`scopes` を伴う `Security` 依存関係](../advanced/security/oauth2-scopes.md) を追加することもできます。

/// tip | 豆知識

      </dependency>
    </dependencies>
  </dependencyManagement>
  <dependencies>
    <dependency>
      <groupId>maven-test</groupId>
      <artifactId>t06-a</artifactId>
      <version>1.0</version>
    </dependency>
    <dependency>
      <groupId>maven-test</groupId>
      <artifactId>t06-c</artifactId>
      <version>1.0</version>
    </dependency>
  </dependencies>
  <build>
    <plugins>

    //                                                                    ================

    /**
     * Testable subclass that bypasses ComponentUtil dependencies.
     * This allows testing the filter logic without requiring the DI container.
     */
    private static class TestableLoadControlFilter extends LoadControlFilter {
        private short cpuPercent = 0;

///

### Імпортуйте `Depends` { #import-depends }

{* ../../docs_src/dependencies/tutorial001_an_py310.py hl[3] *}

### Оголосіть залежність у «залежному» { #declare-the-dependency-in-the-dependant }

Так само, як ви використовуєте `Body`, `Query` тощо з параметрами вашої *функції операції шляху*, використовуйте `Depends` з новим параметром:

{* ../../docs_src/dependencies/tutorial001_an_py310.py hl[13,18] *}