<build>
        <plugins>
          <plugin>
            <artifactId>plugin-all-profiles</artifactId>
            <executions>
              <execution>
                <id>Active all ||${project.basedir}||</id>
                <configuration>
                  <plugin-all-profiles-in>Active all ||${project.basedir}||</plugin-all-profiles-in>
                </configuration>
              </execution>
            </executions>

            Other values define only the prefix of classes/resources being exposed. Their binary name must be equal to the prefix or starting with the prefix (followed by "." or "$").

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

    Test that POM interpolation uses the property values from the dominant profile source (POM vs. settings.xml).
    This boils down to the proper order of profile injection and interpolation, i.e.
    interpolate after profiles from all sources are injected.
  </description>

  <properties>
    <!-- collect the effective property values as derived by interpolation -->
    <pomVsSettingsInterpolated>${pomVsSettings}</pomVsSettingsInterpolated>

  <artifactId>coreit</artifactId>
  <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>
    <!--

      with the current POM.

      NOTE: This list will contain entries for repositories specified by ancestor POMs, including
      the default built-in super-POM, which is the parent of all POMs.
    ]]></description>
  </expression>
  <expression>
    <syntax>project.pluginArtifactRepositories</syntax>
    <configuration>
      <![CDATA[
<pluginRepositories>
  ...
</pluginRepositories>

      <plugin>
        <groupId>org.apache.maven.its.plugins</groupId>
        <artifactId>maven-it-plugin-configuration</artifactId>
        <version>2.1-SNAPSHOT</version>
        <configuration>
          <!--
          All of these values should override the ones inherited from the parent. In particular, collections should not
          be merged with the values given by the parent POM.
          -->
          <propertiesFile>PASSED</propertiesFile>

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