<type>pom</type>
                <scope>import</scope>
            </dependency>
            <dependency>
                <groupId>org.junit</groupId>
                <artifactId>bom</artifactId>
                <version>0.2</version>
                <type>pom</type>
                <scope>import</scope>
            </dependency>
            <dependency>
                <groupId>org.junit</groupId>

                <type>pom</type>
                <scope>import</scope>
            </dependency>
            <dependency>
                <groupId>org.junit</groupId>
                <artifactId>bom</artifactId>
                <version>0.2</version>
                <type>pom</type>
                <scope>import</scope>
            </dependency>
        </dependencies>
    </dependencyManagement>

#!/bin/bash

set -eu

./mvnw clean install --projects '!guava-testlib,!guava-tests,!guava-bom,!guava-gwt' -Dmaven.test.skip=true -Dmaven.javadoc.skip=true
./mvnw clean install --projects '!guava-testlib,!guava-tests,!guava-bom' -Dmaven.test.skip=true -Dmaven.javadoc.skip=true -f android

# We run this separately so that its change to the default toolchain doesn't affect anything else.

  <modelVersion>4.0.0</modelVersion>

  <groupId>com.google.guava</groupId>
  <artifactId>guava-bom</artifactId>
  <version>999.0.0-HEAD-android-SNAPSHOT</version>
  <packaging>pom</packaging>

  <name>Guava BOM</name>
  <description>BOM for Guava artifacts</description>
  <url>https://github.com/google/guava</url>
  <inceptionYear>2010</inceptionYear>

  <licenses>
    <license>

if (androidBuild.toBoolean()) {
  include(":regression-test")
}

if (graalBuild.toBoolean()) {
  include(":native-image-tests")
}

include(":okcurl")
include(":okhttp")
include(":okhttp-bom")
include(":okhttp-brotli")
include(":okhttp-coroutines")
include(":okhttp-dnsoverhttps")
include(":okhttp-hpacktests")
include(":okhttp-idna-mapping-table")
include(":okhttp-java-net-cookiejar")

| <<<pom>>>             |               | <= type>   | none      |                       |                       |
*-----------------------+---------------+------------+-----------+-----------------------+-----------------------+
| <<<bom>>> *           |               | <<<pom>>>  | none      |                       |                       |
*-----------------------+---------------+------------+-----------+-----------------------+-----------------------+

        final byte[] xmlBytes = xml.getBytes();
        final byte[] dataWithBOM = new byte[bom.length + xmlBytes.length];
        System.arraycopy(bom, 0, dataWithBOM, 0, bom.length);
        System.arraycopy(xmlBytes, 0, dataWithBOM, bom.length, xmlBytes.length);

        final InputStream in = new ByteArrayInputStream(dataWithBOM);

        for (MavenProject p : projectsInRequestScope) {
            if ("bom".equals(p.getPackaging())) {
                LOGGER.info(
                        "The packaging attribute of the '{}' project is configured as 'bom' and changed to 'pom'",
                        p.getName());
                p.setPackaging("pom");
            }
        }
    }

<?xml version="1.0" encoding="UTF-8"?>
<metadata>
  <groupId>org.apache.maven.its</groupId>
  <artifactId>bom</artifactId>
  <version>0.1</version>
  <versioning>
    <versions>
      <version>0.1</version>
    </versions>
  </versioning>

Implantar uma aplicação significa executar as etapas necessárias para torná-la disponível para os usuários.

Para uma **web API**, isso normalmente envolve colocá-la em uma **máquina remota**, com um **programa de servidor** que ofereça bom desempenho, estabilidade, etc., de modo que seus **usuários** possam **acessar** a aplicação com eficiência e sem interrupções ou problemas.