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 base directory name of this project deliberately does not match its artifact id! -->

  <parent>
    <groupId>org.apache.maven.its.mng3846</groupId>
    <artifactId>parent</artifactId>
    <version>0.1</version>

"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied.  See the License for the
specific language governing permissions and limitations
under the License.
-->

<!--
NOTE: This POM's XML declaration intentionally declares Latin-1 encoding.
-->

<project>
  <modelVersion>4.0.0</modelVersion>

  <groupId>org.apache.maven.its.mng2254</groupId>
  <artifactId>latin-1</artifactId>

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

            <id>child-2</id>
            <phase>validate</phase>
            <goals>
              <goal>child-2</goal>
            </goals>
          </execution>
          <execution>
            <!-- NOTE: <id> deliberately omitted to use default value -->
            <phase>validate</phase>
            <goals>
              <goal>child-default</goal>
            </goals>
          </execution>
        </executions>

    </dependency>
    <dependency>
      <groupId>org.apache.maven.its.mng4003</groupId>
      <artifactId>d</artifactId>
      <version>1</version>
    </dependency>
  </dependencies>

  <build>
    <!-- NOTE: The combination with a plugin management section is an essential part of the test -->
    <pluginManagement>
      <plugins>
        <plugin>
          <artifactId>maven-clean-plugin</artifactId>

    </dependency>
    <dependency>
      <groupId>org.apache.maven.its.mng4003</groupId>
      <artifactId>d</artifactId>
      <version>1</version>
    </dependency>
  </dependencies>

  <build>
    <!-- NOTE: The combination with a plugin section is an essential part of the test -->
    <plugins>
      <plugin>
        <artifactId>maven-clean-plugin</artifactId>
        <version>2.3</version>
      </plugin>
    </plugins>

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