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

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

 * followed by <dfn>flattening</dfn> and <dfn>resolution</dfn>.
 * The version selection is done for each dependency during the collection phase.
 * The flatten phase keeps only a single version per ({@code groupId}, {@code artifactId}) pair.
 * The resolution phase actually downloads the dependencies (or artifacts) that have been computed.
 *
 * @since 4.0.0
 */

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

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

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

  <groupId>maven-test</groupId>
  <artifactId>t09-b</artifactId>
  <packaging>jar</packaging>
  <version>1.0</version>

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

3. Copier le fichier des dépendances vers le répertoire `/code`.

    Copier **uniquement** le fichier des dépendances en premier, pas le reste du code.

    Comme ce fichier **ne change pas souvent**, Docker le détectera et utilisera le **cache** pour cette étape, ce qui activera le cache pour l'étape suivante aussi.

4. Installer les dépendances listées dans le fichier des dépendances.

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

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

# Header

{* ../../docs_src/dependencies/tutorial013_an_py310.py ln[19:21] *}

Some text

{* ../../docs_src/bigger_applications/app_an_py310/internal/admin.py hl[3] title["app/internal/admin.py"] *}

Some more text

{* ../../docs_src/dependencies/tutorial013_an_py310.py ln[30:38] hl[31:33] *}

And even more text

                    Failed to automatically fix project build files.
                    Make sure each project has a gradleModule.computedRuntimes block directly below the dependencies block:

                    ```
                    dependencies {
                        // ...
                    }

                    gradleModule {
                        computedRuntimes {
                        }