<artifactId>maven-it-plugin-a</artifactId>
        <version>2.1-SNAPSHOT</version>
        <executions>
          <execution>
            <!-- NOTE: Explicitly reference "default" id here -->
            <id>default</id>
            <phase>child-default</phase>
          </execution>
          <execution>
            <id>non-default</id>
            <phase>child-non-default</phase>

            <phase>validate</phase>
            <goals>
              <goal>log-string</goal>
            </goals>
          </execution>
          <execution>
            <!-- NOTE: <id> deliberately omitted here! -->
            <phase>validate</phase>
            <goals>
              <goal>log-string</goal>
            </goals>
          </execution>
        </executions>
      </plugin>
    </plugins>
  </build>

        <artifactId>maven-it-plugin-a</artifactId>
        <version>2.1-SNAPSHOT</version>
        <executions>
          <execution>
            <!-- NOTE: Explicitly reference "default" id here -->
            <id>default</id>
            <phase>child-default</phase>
          </execution>
          <execution>
            <id>non-default</id>
            <phase>child-non-default</phase>

            <type>String</type>
            <multiplicity>*</multiplicity>
          </association>
          <description><![CDATA[Artifacts in the format <code>groupId:artifactId</code>. All the ones listed here are filtered (i.e. removed) from plugin and build extension class realms,
          i.e. referencing any of those coordinates in plugin/build extension dependencies has no effect.]]>
          </description>
        </field>

            lifecycle unless referenced. Any local configuration for a given plugin will override
            the plugin's entire definition here.</description>
          <association>
            <type>PluginManagement</type>
          </association>
        </field>
      </fields>
      <codeSegments>
        <codeSegment>

         its builds. Thus, GWT doesn't get j2objc-annotations transitively, in
         contrast to the other deps of `guava`, which it does get transitively.
         (Arguably we should redeclare *all* the `guava` deps here.) -->
    <dependency>
      <groupId>com.google.j2objc</groupId>
      <artifactId>j2objc-annotations</artifactId>
    </dependency>
    <dependency>
      <groupId>com.google.guava</groupId>

          <artifactId>maven-it-plugin-a</artifactId>
          <version>2.1-SNAPSHOT</version>
          <executions>
            <execution>
              <!-- NOTE: Implicitly reference "default" id here, i.e. omit the <id> element -->
              <phase>parent-default</phase>
            </execution>
            <execution>
              <id>non-default</id>
              <phase>parent-non-default</phase>

        <artifactId>maven-it-plugin-a</artifactId>
        <version>2.1-SNAPSHOT</version>
        <executions>
          <execution>
            <!-- NOTE: Implicitly reference "default" id here, i.e. omit the <id> element -->
            <phase>parent-default</phase>
          </execution>
          <execution>
            <id>non-default</id>
            <phase>parent-non-default</phase>
          </execution>

   |
   | For example, if you have an integration testing plugin - like cactus - that needs to know where
   | your Tomcat instance is installed, you can provide a variable here such that the variable is
   | dereferenced during the build process to configure the cactus plugin.
   |
   | As noted above, profiles can be activated in a variety of ways. One way - the activeProfiles

  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.its.plugins</groupId>
        <artifactId>maven-it-plugin-a</artifactId>
        <!-- NOTE: <version> element deliberately omitted here -->
        <executions>
          <execution>
            <id>child-1</id>
            <phase>child-1</phase>
          </execution>
          <execution>
            <id>child-2</id>