<version>1.0-SNAPSHOT</version>

  <name>Maven Integration Test :: MNG-3760</name>
  <description>
    Test interpolation of ${project.baseUri}
  </description>

  <properties>
    <!-- this is where we collect all the interpolated values for the POM dump -->
    <prop1>${project.baseUri}</prop1>
  </properties>

            <!-- Even after we stop using JSR305 annotations in our own code, we'll want this link so that NullPointerTester's docs can link to @CheckForNull and friends... at least once we start using this config for guava-testlib. -->
            <offlineLink>

            of those modules are ones that it uses but forgets to list in its own <inherits>, we'd
            like to get an error. Currently we do, but if we add the extra <inherits> lines, we
            won't.

            I have one idea for a better approach, but it's painful, and I haven't tested it: We
            could postprocess Collect.gwt.xml to add <skip> lines for all the files that should be

  <name>Maven Integration Test :: MNG-3900</name>
  <description>
    Test that build properties defined via active profiles are used for
    interpolation.
  </description>

  <!--
    These are some POM elements we would like to interpolate with
    properties from the profile.
  -->
  <url>https://maven.apache.org/${test}
  </url>
  <properties>
    <test>FAILED</test>
    <property>${test}</property>
  </properties>

  <name>Maven Integration Test :: MNG-3822</name>
  <description>
    Verify that POM interpolation uses basedir-aligned build directories.
  </description>

  <properties>
    <!-- this is where we collect all the interpolated values for the POM dump -->
    <buildMainSrc>${project.build.sourceDirectory}</buildMainSrc>
    <buildTestSrc>${project.build.testSourceDirectory}</buildTestSrc>

      <releases>
        <!-- That's the boolean POM field we would like to interpolate -->
        <enabled>${releasesEnabled}</enabled>
      </releases>
    </repository>
  </repositories>

  <build>
    <resources>
      <resource>
        <directory>src/main/resources</directory>
        <!-- That's the boolean POM field we would like to interpolate -->
        <filtering>${filter.resources}</filtering>

      <groupId>com.google.truth</groupId>
      <artifactId>truth</artifactId>
      <version>${truth.version}</version>
      <scope>test</scope>
      <exclusions>
        <exclusion>
          <!-- use the guava we're building. -->
          <groupId>com.google.guava</groupId>
          <artifactId>guava</artifactId>
        </exclusion>
      </exclusions>
    </dependency>
  </dependencies>
  <build>
    <plugins>

      <groupId>com.google.truth</groupId>
      <artifactId>truth</artifactId>
      <version>${truth.version}</version>
      <scope>test</scope>
      <exclusions>
        <exclusion>
          <!-- use the guava we're building. -->
          <groupId>com.google.guava</groupId>
          <artifactId>guava</artifactId>
        </exclusion>
      </exclusions>
    </dependency>
  </dependencies>
  <build>
    <plugins>

                   If we're building with JDK8, then clearly we're sticking to
                   JDK8 APIs. However, I assume (but did not confirm) that we'd
                   have the same issue with our -android builds, which need
                   animal-sniffer so that they can check that we're sticking to
                   JDK6-like APIs.

                   So instead, we use javac9, which doesn't lead to this error.

            <!-- Even after we stop using JSR305 annotations in our own code, we'll want this link so that NullPointerTester's docs can link to @CheckForNull and friends... at least once we start using this config for guava-testlib. -->
            <offlineLink>