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 "$").

  <name>Maven Integration Test :: MNG-4129 :: Child-1</name>
  <description>
    Verify that plugin executions defined in the parent with inherited=false are not executed in child modules.
  </description>

  <build>
    <plugins>
      <!-- NOTE: It's essential part of this test variant to redefine the test plugin again, i.e. trigger plugin merging -->
      <plugin>
        <groupId>org.apache.maven.its.plugins</groupId>

    as defined by the child. This boils down to the order of inheritance and (parent) interpolation.
  </description>

  <properties>
    <overridden>PARENT</overridden>
    <!-- Test the effective value of this property in the child when "overridden" is defined by child as well -->
    <interpolated>${overridden}</interpolated>
  </properties>

  <packaging>jar</packaging>

  <name>Maven Integration Test :: MNG-4102 :: Child</name>
  <description>
    Verify that the effective value of an inherited property reflects the values of any nested property
    as defined by the child. This boils down to the order of inheritance and (parent) interpolation.
  </description>

  <properties>
    <overridden>CHILD</overridden>
  </properties>

  <profiles>
    <profile>

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

  <name>Maven Integration Test :: MNG-4129</name>
  <description>
    Verify that plugin executions defined in the parent with inherited=false are not executed in child modules.
  </description>

  <modules>
    <module>child-1</module>
    <module>child-2</module>
  </modules>

  <build>
    <plugins>

   | value of '1.4' might activate a profile when the build is executed on a JDK version of '1.4.2_07'.
   | Finally, the list of active profiles can be specified directly from the command line.
   |
   | NOTE: For profiles defined in the settings.xml, you are restricted to specifying only artifact
   |       repositories, plugin repositories, and free-form properties to be used as configuration
   |       variables for plugins in the POM.
   |
   |-->

            define its own format and semantics. This was generally a properties format.
            <p>Since Maven 3.2.4, the type for this field has been changed to Properties to match the de-facto
            format.
            <p>Each toolchain defines its own properties names and semantics.
          </description>
        </field>
        <field>

  <groupId>org.apache.maven.its.mng4034</groupId>
  <artifactId>child</artifactId>
  <version>1.0-SNAPSHOT</version>

  <name>Maven Integration Test :: MNG-4034</name>
  <description>
    Verify that dependencies defined in profiles are subject to the dependency management of the parent.
  </description>

  <profiles>
    <profile>
      <id>maven-core-it</id>
      <activation>
        <activeByDefault>true</activeByDefault>

  <name>Maven Integration Test :: MNG-4129 :: Child-2</name>
  <description>
    Verify that plugin executions defined in the parent with inherited=false are not executed in child modules.
  </description>

  <build>
    <plugins>
      <!-- NOTE: It's essential part of this test variant to *not* define the test plugin again, i.e. bypass plugin merging -->
    </plugins>
  </build>

        </field>
        <field>
          <name>phase</name>
          <version>1.0.0+</version>
          <type>String</type>
          <description>
            Defines a default phase to bind a Mojo execution to if the user does not explicitly set a phase in the POM.
            &lt;p>&lt;b>Note:&lt;/b> This will not automagically make a Mojo run when the plugin declaration is added