<dependencies>
      <dependency>
        <groupId>maven-test</groupId>
        <artifactId>t07-b</artifactId>
        <version>1.0</version>
      </dependency>
      <dependency>
        <groupId>maven-test</groupId>
        <artifactId>t07-d</artifactId>
        <version>1.0</version>
        <scope>test</scope>
        <optional>false</optional>
      </dependency>
    </dependencies>

        // packaging type.
        for (Dependency dependency : dependencies) {
            String key = dependency.getGroupId() + ":" + dependency.getArtifactId() + ":" + dependency.getVersion()
                    + (dependency.getClassifier() != null ? ":" + dependency.getClassifier() : EMPTY);
            String mKey = m.getGroupId() + ":" + m.getArtifactId() + ":" + m.getVersion();

  <dependencies>

    <dependency>
      <groupId>maven-test-compile</groupId>
      <artifactId>scope-default</artifactId>
      <version>1.0</version>
    </dependency>

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

    <dependency>
      <groupId>maven-test-compile</groupId>

We can do better...

## What makes a dependency { #what-makes-a-dependency }

Up to now you have seen dependencies declared as functions.

But that's not the only way to declare dependencies (although it would probably be the more common).

The key factor is that a dependency should be a "callable".

A "**callable**" in Python is anything that Python can "call" like a function.

  <dependencyManagement>

    <dependencies>

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

      <dependency>
        <groupId>maven-test</groupId>
        <artifactId>t04-b</artifactId>
        <version>1.0</version>
      </dependency>

    <dependency>
      <groupId>maven-test</groupId>

  <description>Maven 4 API - Maven SPI.</description>

  <dependencies>
    <dependency>
      <groupId>org.apache.maven</groupId>
      <artifactId>maven-api-annotations</artifactId>
    </dependency>
    <dependency>
      <groupId>org.apache.maven</groupId>
      <artifactId>maven-api-model</artifactId>
    </dependency>
    <dependency>
      <groupId>org.apache.maven</groupId>
      <artifactId>maven-api-core</artifactId>

          <version>2.1-SNAPSHOT</version>
          <dependencies>
            <dependency>
              <groupId>org.apache.maven.its.mng3906</groupId>
              <artifactId>e</artifactId>
              <version>0.1</version>
            </dependency>
            <dependency>
              <groupId>org.apache.maven.its.mng3906</groupId>
              <artifactId>a</artifactId>

Esto es bastante simple (no muy útil), pero nos ayudará a centrarnos en cómo funcionan las sub-dependencias.

## Segunda dependencia, "dependable" y "dependant" { #second-dependency-dependable-and-dependant }

Luego puedes crear otra función de dependencia (un "dependable") que al mismo tiempo declare una dependencia propia (por lo que también es un "dependant"):

{* ../../docs_src/dependencies/tutorial005_an_py310.py hl[13] *}

    <dependencyManagement>
        <dependencies>
            <dependency>
                <groupId>test</groupId>
                <artifactId>other</artifactId>
                <version>0.1-SNAPSHOT</version>
                <type>pom</type>
                <scope>import</scope>
            </dependency>
            <dependency>
                <groupId>org.junit</groupId>
                <artifactId>bom</artifactId>

                        <dependencies>
                            <dependency>
                                <groupId>org.apache.commons</groupId>
                                <artifactId>commons-lang3</artifactId>
                                <version>3.12.0</version>
                            </dependency>
                            <dependency>
                                <groupId>org.apache.commons</groupId>