comprehension tool. Based on the concept of a project object model:
    builds, dependency management, documentation creation, site
    publication, and distribution publication are all controlled from
    the declarative file. Maven can be extended by plugins to utilise a
    number of other development tools for reporting or the build
    process.
  </description>
  <url>http://maven.apache.org/</url>

          </association>
        </field>
        <field>
          <name>configuration</name>
          <version>1.0.0</version>
          <type>DOM</type>
          <description>Configuration to pass to all goals run in this phase.</description>
        </field>
      </fields>
    </class>
    <class>
      <name>Execution</name>
      <version>1.0.0</version>
      <description>A set of goals to execute.</description>

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

    comprehension tool. Based on the concept of a project object model:
    builds, dependency management, documentation creation, site
    publication, and distribution publication are all controlled from
    the declarative file. Maven can be extended by plugins to utilise a
    number of other development tools for reporting or the build
    process.
  </description>
  <url>http://maven.apache.org/</url>

 |
 |                 -t /path/to/user/toolchains.xml
 |
 |  2. Global Level. This toolchains.xml file provides configuration for all Maven
 |                 users on a machine (assuming they're all using the same Maven
 |                 installation). It's normally provided in
 |                 ${maven.conf}/toolchains.xml.
 |

    if match is found, the toolchain instance is made available to other Maven plugins.</p>
    <p>With {@code jdk} toolchain, for example, instead of being stuck with the JDK used to run Maven, all plugins can use
    the same other JDK instance without hardcoding absolute paths into the {@code pom.xml}
    and without configuring every plugin that require path to JDK tools.</p>

    buffer size (usually 4 or 8 KB). The text block is designed such that its length is exactly 32 KB after leading
    and trailing whitespace has been removed and all line terminators have been removed.
    -->
    <prop2>
00 KB     1         2         3         4         5         6  X
0         1         2         3         4         5         6  X

      <reporting>
        <plugins>
          <plugin>
            <artifactId>plugin-all-profiles</artifactId>
            <reportSets>
              <reportSet>
                <id>Active all ||${project.basedir}||</id>
                <configuration>
                  <plugin-all-profiles-in>Active all ||${project.basedir}||</plugin-all-profiles-in>
                </configuration>
              </reportSet>
            </reportSets>

 |
 |                 -s /path/to/user/settings.xml
 |
 |  2. Global Level. This settings.xml file provides configuration for all Maven
 |                 users on a machine (assuming they're all using the same Maven
 |                 installation). It's normally provided in
 |                 ${maven.conf}/settings.xml.
 |

  <artifactId>parent</artifactId>
  <version>0.1</version>
  <packaging>pom</packaging>

  <name>Maven Integration Test :: MNG-3845</name>
  <description>
    Test that inheritance is all-or-nothing for certain subtrees of the POM.
  </description>

  <organization>
    <name>parent-org</name>
    <url>https://parent.url/org</url>
  </organization>

  <scm>