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

        xml.append("</project>\n");
        return xml.toString();
    }

    public Document buildDocument() {
        try {
            String xmlContent = build();
            Editor editor = new Editor(Document.of(xmlContent));
            return editor.document();

        if: always()
        with:
          name: initial-mimir-logs
          include-hidden-files: true
          retention-days: 1
          path: |
            ~/.mimir/*.log

  full-build:
    needs: initial-build
    runs-on: ${{ matrix.os }}
    strategy:
      fail-fast: false
      matrix:
        os: [ubuntu-latest, macos-latest, windows-latest]
        java: ['17', '21', '25']
    steps:

```Dockerfile
COPY ./app /code/app
```

### Build the Docker Image { #build-the-docker-image }

Now that all the files are in place, let's build the container image.

* Go to the project directory (in where your `Dockerfile` is, containing your `app` directory).
* Build your FastAPI image:

<div class="termy">

```console
$ docker build -t myimage .

---> 100%
```

</div>

  <version>1.1</version>
  <build>
    <plugins>
      <plugin>
        <artifactId>maven-surefire-plugin</artifactId>
        <configuration>
          <excludes>
            <exclude>org/codehaus/plexus/util/FileBasedTestCase.java</exclude>
            <exclude>**/Test*.java</exclude>
          </excludes>
        </configuration>
      </plugin>
    </plugins>
  </build>
  <distributionManagement>

    <mailingList>
      <name>blah</name>
    </mailingList>
  </mailingLists>

  <build>
      <testSourceDirectory>../sibling/src-test</testSourceDirectory>
      <sourceDirectory>../sibling/src-main</sourceDirectory>
      <resources>
        <resource><directory>blah</directory></resource>
      </resources>
  </build>

 *   <li>{@link org.apache.maven.api.model.Plugin} - Represents a Maven plugin configuration</li>
 *   <li>{@link org.apache.maven.api.model.Build} - Contains build configuration information</li>
 *   <li>{@link org.apache.maven.api.model.Profile} - Represents a build profile for conditional execution</li>
 * </ul>
 *
 * @since 4.0.0
 */

/**
 * Represents a Java toolchain in the Maven build system.
 *
 * <p>A Java toolchain is a specific type of toolchain that provides access
 * to Java development tools, such as the Java compiler and Java runtime
 * environment. This interface allows users to define and configure
 * Java-related toolchains that can be utilized during the build process
 * in Maven.</p>
 *

            pomMap.put(Paths.get("project", "module-b", "pom.xml"), moduleBDoc);

            Element moduleBRoot = moduleBDoc.root();
            Element build = moduleBRoot.child("build").orElse(null);
            Element plugins = build.child("plugins").orElse(null);
            Element plugin = plugins.child("plugin").orElse(null);
            Element dependencies = plugin.child("dependencies").orElse(null);

# We run this separately so that its change to the default toolchain doesn't affect anything else.
# (And we run it after the main build so that that build has already downloaded Java 11 if necessary.)
./mvnw --projects '!guava-testlib,!guava-tests,!guava-bom,!guava-gwt' initialize -P print-java-11-home
export JAVA_HOME=$(<target/java_11_home)

One or more test dependencies are not in the pip package.
If these test dependencies need to be in the TensorFlow pip package, please
add them to //tensorflow/tools/pip_package/BUILD. Otherwise, add the no_pip tag
to the test, or change code_check_full.bats in the SIG Build repository. That's
https://github.com/tensorflow/tensorflow/blob/master/tensorflow/tools/tf_sig_build_dockerfiles/devel.usertools/code_check_full.bats
Here are the affected tests: