KIND, either express or implied.  See the License for the
specific language governing permissions and limitations
under the License.
-->

<project>
  <modelVersion>4.0.0</modelVersion>

  <!-- NOTE: The ugly formatting is essential part of this test! -->
  <parent>
    <groupId>   org.apache.maven.its.mng4070   </groupId>
    <artifactId>  parent  </artifactId>
    <version>  1.0  </version>
  </parent>

under the License.
-->

<project>
  <modelVersion>4.0.0</modelVersion>

  <groupId>org.apache.maven.its.mng4341</groupId>
  <artifactId>test</artifactId>
  <version>0.1</version>
  <!-- NOTE: The upper-case packaging name is intentional and triggers a special mode in the EmptyLifecycleExecutor -->
  <packaging>JAR</packaging>

  <name>Maven Integration Test :: MNG-4341</name>
  <description>

KIND, either express or implied.  See the License for the
specific language governing permissions and limitations
under the License.
-->

<project>
  <modelVersion>4.0.0</modelVersion>

  <!-- NOTE: The ugly formatting is essential part of this test! -->
  <groupId>
    org.apache.maven.its.mng4070
  </groupId>
  <artifactId>
    parent
  </artifactId>
  <version>
    1.0
  </version>
  <packaging>

      <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 -->
            <id>default</id>
            <phase>child-default</phase>
          </execution>
          <execution>
            <id>non-default</id>

          <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
            to the POM. It merely enables the user to omit the {@code &lt;phase&gt;} element from the

  <description>
    Verify that attributes in plugin configuration elements are not erroneously duplicated to other elements when
    plugin management and a profile are used.
  </description>

  <build>
    <!-- NOTE: This test used plugin management for the IT plugin -->
    <pluginManagement>
      <plugins>
        <plugin>
          <groupId>org.apache.maven.its.plugins</groupId>

          <artifactId>maven-it-plugin-configuration</artifactId>
          <version>2.1-SNAPSHOT</version>
          <inherited>true</inherited>
          <configuration>
            <listParam>
              <!-- NOTE: These values are deliberately not in alpha order! -->
              <listParam>PARENT-1</listParam>
              <listParam>PARENT-3</listParam>
              <listParam>PARENT-2</listParam>

    <groupId>org.apache.maven.its.mng0522</groupId>
    <artifactId>parent</artifactId>
    <version>1.0-SNAPSHOT</version>
  </parent>

  <artifactId>child-project</artifactId>
  <version>1.0-SNAPSHOT</version>
  <!-- NOTE: The upper-case packaging name is intentional and triggers a special mode in the EmptyLifecycleExecutor -->
  <packaging>JAR</packaging>

  <build>
    <plugins>
      <plugin>

    plugin version than the parent.
  </description>

  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.its.plugins</groupId>
        <artifactId>maven-it-plugin-a</artifactId>
        <!-- NOTE: Use different version than parent -->
        <version>2.0</version>
        <executions>
          <execution>
            <id>child-1</id>
            <phase>child-1</phase>
          </execution>

      <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 -->
            <id>default</id>
            <phase>child-default</phase>
          </execution>
          <execution>
            <id>non-default</id>