default id, regardless whether the id is given explicitly by the user or implicitly assumed from defaults.
  </description>

  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.its.plugins</groupId>
        <artifactId>maven-it-plugin-a</artifactId>
        <version>2.1-SNAPSHOT</version>
        <executions>
          <execution>
            <!-- NOTE: Explicitly reference "default" id here -->

        <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

    default id, regardless whether the id is given explicitly by the user or implicitly assumed from defaults.
  </description>

  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.its.plugins</groupId>
        <artifactId>maven-it-plugin-a</artifactId>
        <version>2.1-SNAPSHOT</version>
        <executions>
          <execution>
            <!-- NOTE: Explicitly reference "default" id here -->

  <description>
    Test that plugin executions with the same id are merged during inheritance, especially executions using the
    default id, regardless whether the id is given explicitly by the user or implicitly assumed from defaults.
  </description>

  <build>
    <!-- This project uses plugin management for the test plugin -->
    <pluginManagement>
      <plugins>
        <plugin>

  <description>
    Test that plugin executions with the same id are merged during inheritance, especially executions using the
    default id, regardless whether the id is given explicitly by the user or implicitly assumed from defaults.
  </description>

  <build>
    <!-- This project does not use plugin management for the test plugin -->
    <plugins>
      <plugin>

          <artifactId>a</artifactId>
          <version>0.1</version>
        </dependency>
      </dependencies>
    </profile>
    <profile>
      <id>profile-2</id>
      <!-- to be activated explicitly on the CLI by its id -->
      <dependencies>
        <dependency>
          <groupId>org.apache.maven.its.it0021</groupId>
          <artifactId>b</artifactId>
          <version>0.1</version>
        </dependency>

          </configuration>
        </plugin>
        <plugin>
          <!-- this checks handling of a plugin which is explicitly bound to the lifecycle -->
          <groupId>org.apache.maven.its.plugins</groupId>
          <artifactId>maven-it-plugin-log-file</artifactId>
          <version>2.1-SNAPSHOT</version>
          <configuration>
            <logFile>passed.txt</logFile>
          </configuration>

      </plugin>
      <plugin>
        <artifactId>maven-javadoc-plugin</artifactId>
        <configuration>
          <!-- Passing `-subpackages com.google.common` breaks things, so we explicitly exclude everything else instead. -->
          <!-- excludePackageNames requires specification of packages separately from "all subpackages".
               https://issues.apache.org/jira/browse/MJAVADOC-584 -->

        <field>
          <name>version</name>
          <version>4.0.0+</version>
          <description>
            The version of the reporting plugin to be used. Starting with Maven 3, if no version is defined explicitly,
            version is searched in {@code build/plugins} then in {@code build/pluginManagement}.
          </description>
          <type>String</type>
        </field>
        <field>

      </plugin>
      <plugin>
        <artifactId>maven-javadoc-plugin</artifactId>
        <configuration>
          <!-- Passing `-subpackages com.google.common` breaks things, so we explicitly exclude everything else instead. -->
          <!-- excludePackageNames requires specification of packages separately from "all subpackages".
               https://issues.apache.org/jira/browse/MJAVADOC-584 -->