<description>A preferred alternative to this expression, in the case where it's deprecated.</description>
          <type>String</type>
        </field>
        <field>
          <version>1.0.0</version>
          <name>ban</name>
          <description>A preferred alternative to this expression, in the case where it's banned from use.</description>
          <type>String</type>
        </field>

            associated with a Maven project can lack a file. As such, this annotation is meant for Mojos that only
            want to analyze the set of transitive dependencies, in particular during early lifecycle phases where
            full dependency resolution might fail due to projects which haven't been built yet.
          </description>
        </field>
        <field>
          <name>dependencyCollection</name>

 |
 |                 -gs /path/to/global/settings.xml
 |
 | The sections in this sample file are intended to give you a running start at
 | getting the most out of your Maven installation. Where appropriate, the default
 | values (values used when the setting is not specified) are provided.
 |
 |-->
<settings xmlns="http://maven.apache.org/SETTINGS/1.3.0"
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

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

  <name>Maven Integration Test :: MNG-3944</name>
  <description>
    Test that interpolation of ${basedir} works for a POM that is not named "pom.xml"
  </description>

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

  <version>0.1</version>
  <packaging>jar</packaging>

  <name>Maven Integration Test :: MNG-3833</name>
  <description>
    Test that POM interpolation fully interpolates all properties in data flow chain, i.e. where property
    A depends on property B, and property B depends on property C and so on.
  </description>

  <properties>
    <!--

  </ciManagement>
  <modules>
    <module>guava</module>
    <module>guava-bom</module>
    <module>guava-testlib</module>
    <module>guava-tests</module>
  </modules>
  <build>
    <!-- Handle where Guava deviates from Maven defaults -->
    <sourceDirectory>src</sourceDirectory>
    <testSourceDirectory>test</testSourceDirectory>
    <resources>
      <resource>
        <directory>../..</directory>
        <includes>

          <description>
            The directory where compiled application classes are placed.
            The default value is {@code target/classes}.
          </description>
          <type>String</type>
        </field>
        <field>
          <name>testOutputDirectory</name>
          <version>4.0.0+</version>
          <description>
            The directory where compiled test classes are placed.

  </description>

  <properties>
    <!-- That's the property containing escaped XML markup -->
    <xmlMarkup>&lt;?xml version='1.0'?&gt;Tom&amp;Jerry</xmlMarkup>
    <!-- That's a property where the above property will be resolved -->
    <xmlTest>${xmlMarkup}</xmlTest>
  </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>