comprehension tool. Based on the concept of a project object model:
    builds, dependency management, documentation creation, site
    publication, and distribution publication are all controlled from
    the declarative file. Maven can be extended by plugins to utilise a
    number of other development tools for reporting or the build
    process.
  </description>
  <url>http://maven.apache.org/</url>

  <version>0.1</version>
  <packaging>jar</packaging>

  <name>Maven Integration Test :: MNG-3900</name>
  <description>
    Test that build properties defined via active profiles are used for
    interpolation.
  </description>

  <!--
    These are some POM elements we would like to interpolate with
    properties from the profile.
  -->
  <url>https://maven.apache.org/${test}
  </url>
  <properties>
    <test>FAILED</test>

  <packaging>JAR</packaging>

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

<project>
  <modelVersion>4.0.0</modelVersion>

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

  <!-- while groupId and version are inherited, artifactId is not and must be specified -->

  </parent>

  <artifactId>child-2</artifactId>

  <name>Maven Integration Test :: MNG-3937</name>
  <description>
    Test that during inheritance/merging of a plugin execution the goals specified by child and parent are properly
    ordered.
  </description>

  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.its.plugins</groupId>
        <artifactId>maven-it-plugin-a</artifactId>

  <artifactId>test1</artifactId>
  <version>1.0-SNAPSHOT</version>

  <name>Maven Integration Test :: MNG-4053</name>
  <description>
    Verify that attributes in plugin configuration elements are not erroneously duplicated to other elements when
    no plugin management is used.
  </description>

  <build>
    <!-- NOTE: This test does not use plugin management for the IT plugin -->
    <plugins>
      <plugin>

  <artifactId>test</artifactId>
  <version>0.1</version>
  <packaging>pom</packaging>

  <name>Maven Integration Test :: MNG-3886</name>
  <description>
    Test that the goals from a plugin execution are executed in the order given by the POM, regardless whether
    plugin management is present or not.
  </description>

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

            classes that are actually used in the module under test.

            One way to eliminate the warnings is to make base.testModule include the not really
            necessary <inherits> lines for c.g.c.collect.testModule, etc. However, adding <inherits>
            lines could make c.g.c.base.testModule transitively inherit from extra modules. If some

  <artifactId>parent</artifactId>
  <version>0.1</version>
  <packaging>pom</packaging>

  <name>Maven Integration Test :: MNG-3906</name>
  <description>
    Test that project-level plugin dependencies are properly merged during inheritance.
  </description>

  <build>
    <pluginManagement>
      <plugins>
        <plugin>
          <groupId>org.apache.maven.its.plugins</groupId>

  <artifactId>test</artifactId>
  <version>1.0-SNAPSHOT</version>
  <packaging>jar</packaging>

  <name>Maven Integration Test :: MNG-2309</name>
  <description>
    Test that profiles are injected in declaration order, with the last profile being the most dominant.
  </description>

  <profiles>
    <!-- NOTE: Using intentionally more than two profiles to prevent random test success -->
    <profile>