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

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

    <version>0.1</version>
  </parent>

  <artifactId>child-1</artifactId>

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

  <name>Maven Integration Test :: MNG-4193</name>
  <description>
    Test that multiple artifact repository declarations with the same id cause a validation error even if the
    repositories are defined within a (non-active) profile.
  </description>

  <profiles>
    <profile>
      <id>test</id>
      <repositories>
        <repository>
          <id>one</id>

  <name>Maven Integration Test :: MNG-4008</name>
  <description>
    Verify that filter definitions are properly merged.
  </description>

  <build>
    <filters>
      <!-- NOTE: The first filter is deliberately defined by the child as well, so should not be added twice -->
      <filter>src/main/filters/child-a.properties</filter>
      <filter>src/main/filters/parent-c.properties</filter>
      <filter>src/main/filters/parent-b.properties</filter>

            These dependencies are used to construct a classpath for your
            project during the build process. They are automatically downloaded from the
            repositories defined in this project.

            @see <a href="https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html">Dependency mechanism</a>
          </description>
          <association>

  <name>Maven Integration Test :: MNG-4332</name>
  <description>
    Verify that default plugin executions contributed by the packaging are executed before user-defined
    executions from the POM's build section, regardless whether the executions are defined in the regular
    plugins section or the plugin management section.
  </description>

  <build>
    <pluginManagement>
      <plugins>
        <plugin>