),
        ] = None,
        dependencies: Annotated[
            Optional[Sequence[Depends]],
            Doc(
                """
                A list of global dependencies, they will be applied to each
                *path operation*, including in sub-routers.

                Read more about it in the

<project>
  <modelVersion>4.0.0</modelVersion>
  <groupId>maven-test</groupId>
  <artifactId>t06-b</artifactId>
  <packaging>jar</packaging>
  <version>1.0</version>
  <dependencies>
    <dependency>
      <groupId>maven-test</groupId>
      <artifactId>t06-c</artifactId>
      <version>1.0</version>
      <type>jar</type>
      <scope>compile</scope>
    </dependency>
    <dependency>
      <groupId>maven-test</groupId>

/**
 * Verifies scope inheritance of direct and transitive dependencies.
 *
 * Should show three behaviors:
 *
 * 1. dependencyManagement should override the scope of transitive dependencies.
 * 2. Direct dependencies should override the scope of dependencyManagement.
 * 3. Direct dependencies should inherit scope from dependencyManagement when
 *    they do not explicitly state a scope.
 *
 */

 <<<plexus.core>>> and <<<plexus.core.maven>>> realms at run-time if required.
 Plugins can state compile-time dependencies on any of the resources found in
 the core realms listed above and these dependencies will be included in the
 plugin descriptor that is generated but when running within Maven these
 resources will be filtered out. In other words these resources will not

    <version>0.1-SNAPSHOT</version>
    <packaging>pom</packaging>

    <dependencyManagement>
        <dependencies>
            <dependency>
                <groupId>test</groupId>
                <artifactId>mydep</artifactId>
                <version>0.3</version>
            </dependency>
        </dependencies>
    </dependencyManagement>

    <artifactId>parent</artifactId>
    <version>1.0-SNAPSHOT</version>
  </parent>
  <artifactId>module-b</artifactId>

  <dependencies>
    <dependency>
      <groupId>cyclic-reference</groupId>
      <artifactId>module-a</artifactId>
      <version>1.0-SNAPSHOT</version>
    </dependency>
  </dependencies>

  <artifactId>p0</artifactId>
  <packaging>pom</packaging>
  <name>p0</name>
  <version>1.0</version>
  <organization>
    <name>Codehaus</name>
  </organization>

  <dependencyManagement>

    <dependencies>

      <dependency>
        <groupId>maven-test</groupId>
        <artifactId>t10-a</artifactId>
        <version>1.0</version>
        <scope>test</scope>
      </dependency>

      <dependency>

    <modelVersion>4.0.0</modelVersion>

    <groupId>test</groupId>
    <artifactId>test</artifactId>
    <version>0.1-SNAPSHOT</version>

    <dependencyManagement>
        <dependencies>
            <dependency>
                <groupId>test</groupId>
                <artifactId>mydep</artifactId>
                <version>0.2</version>
            </dependency>
            <dependency>

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

                if dependencies:
                    current_dependencies.extend(dependencies)
                if route.dependencies:
                    current_dependencies.extend(route.dependencies)
                self.add_api_websocket_route(
                    prefix + route.path,
                    route.endpoint,
                    dependencies=current_dependencies,