<url>file://dummy</url>
    </repository>
  </repositories>
  <dependencies>
    <dependency>
      <groupId>maven-test</groupId>
      <artifactId>t05-b</artifactId>
      <version>1.0</version>
      <type>jar</type>
      <scope>compile</scope>
    </dependency>
  </dependencies>

* Even dependencies can have dependencies, creating a hierarchy or **"graph" of dependencies**.
* All **automatically handled** by the framework.
* All the dependencies can require data from requests and **augment the path operation** constraints and automatic documentation.
* **Automatic validation** even for *path operation* parameters defined in dependencies.

        type = Type.COMPOSITE

        applyDefaultSettings()

        features {
            publishBuildStatusToGithub(model)
        }

        dependencies {
            snapshotDependencies(dependencies)
        }

  <packaging>pom</packaging>

  <name>Simple Unit Test Parent</name>

  <dependencyManagement>
    <dependencies>
      <dependency>
        <groupId>ut.simple</groupId>
        <artifactId>dependency</artifactId>
        <version>1.0</version>
      </dependency>
    </dependencies>
  </dependencyManagement>

            throws ArtifactMetadataRetrievalException {
        Set<Artifact> dependencies = new HashSet<>();

        if ("g".equals(artifact.getArtifactId())) {
            Artifact a = null;
            try {
                a = factory.createBuildArtifact("org.apache.maven", "h", "1.0", "jar");
                dependencies.add(a);
            } catch (Exception e) {

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

  <description>Test that reactor projects are included in dependency resolution.</description>

  <dependencies>
    <dependency>
      <groupId>org.apache.maven.its.mng3023</groupId>
      <artifactId>dependency</artifactId>
      <version>1</version>
    </dependency>
  </dependencies>

  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.its.plugins</groupId>

  <version>0.1</version>

    <dependencies>
      <dependency>
        <groupId>test</groupId>
        <artifactId>a</artifactId>
        <version>LATEST</version>
      </dependency>
      <dependency>
        <groupId>test</groupId>
        <artifactId>b</artifactId>
        <version>RELEASE</version>
        </dependency>
    </dependencies>

    <plugins>
      <plugin>
        <artifactId>maven-it-plugin</artifactId>
        <version>1.0</version>
        <dependencies>
          <dependency>
            <!-- groupId missing -->
            <artifactId>a</artifactId>
            <version>2.0</version>
          </dependency>
        </dependencies>
      </plugin>
    </plugins>
  </build>

# Security Tools

When you need to declare dependencies with OAuth2 scopes you use `Security()`.

But you still need to define what is the dependable, the callable that you pass as a parameter to `Depends()` or `Security()`.

There are multiple tools that you can use to create those dependables, and they get integrated into OpenAPI so they are shown in the automatic docs UI, they can be used by automatically generated clients and SDKs, etc.