<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>

            Element dependencies = DomUtils.findChildElement(dependencyManagement, "dependencies");
            var dependencyElements = dependencies.children("dependency").toList();
            assertEquals(1, dependencyElements.size(), "Should have only one dependency after duplicate removal");
        }

        @Test
        @DisplayName("should remove duplicate dependencies in regular dependencies")

                        .append(">\n");
            }
            xml.append("    </properties>\n");
        }

        if (!dependencies.isEmpty()) {
            xml.append("    <dependencies>\n");
            for (Dependency dependency : dependencies) {
                xml.append("        <dependency>\n");
                xml.append("            <groupId>").append(dependency.groupId).append("</groupId>\n");

## Créer une dépendance `get_current_user` { #create-a-get-current-user-dependency }

Créons une dépendance `get_current_user`.

Rappelez-vous que les dépendances peuvent avoir des sous-dépendances ?

`get_current_user` aura une dépendance avec le même `oauth2_scheme` que nous avons créé précédemment.

previous build will be preserved and reused for the subsequent builds.

### Specifying Python dependencies

During bazel build all TensorFlow's Python dependencies are pinned to their
specific versions. This is necessary to ensure reproducibility of the build.
The pinned versions of the full transitive closure of TensorFlow's dependencies
together with their corresponding hashes are specified in

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

/// tip | 豆知識

                // Root level dependencies
                Stream.of(
                                new DependencyContainer(root.child(DEPENDENCIES).orElse(null), DEPENDENCIES),
                                new DependencyContainer(
                                        root.child(DEPENDENCY_MANAGEMENT)
                                                .flatMap(dm -> dm.child(DEPENDENCIES))

      </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>

from fastapi import Depends, FastAPI

from .dependencies import get_query_token, get_token_header
from .internal import admin
from .routers import items, users

app = FastAPI(dependencies=[Depends(get_query_token)])


app.include_router(users.router)
app.include_router(items.router)
app.include_router(
    admin.router,
    prefix="/admin",
    tags=["admin"],
    dependencies=[Depends(get_token_header)],

 Plugins should avoid these classes and be updated to use only Maven3 dependencies (and require Maven3): see
 {{{https://cwiki.apache.org/confluence/display/MAVEN/Plugin+migration+to+Maven3+dependencies} Plugin migration to Maven3 dependencies}}