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>

  <artifactId>subproject</artifactId>

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>
    pom
  </packaging>

  <artifactId>test2</artifactId>
  <version>1.0</version>

  <name>Maven Integration Test :: MNG-3586</name>
  <description>
    Test that plugin dependencies with scope system are part of the plugin class realm.
  </description>

  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.its.plugins</groupId>
        <artifactId>maven-it-plugin</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>
        <artifactId>maven-it-plugin-log-file</artifactId>

      <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>
          <version>2.3</version>
        </plugin>
      </plugins>

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

          <defaultValue>true</defaultValue>
        </field>
        <field>
          <name>requiresReports</name>
          <version>1.0.0</version><!-- no longer part of 1.1.0 -->
          <type>boolean</type>
          <description>Flags this Mojo to require running inside of a reports context. Unsupported since Maven 3.0.</description>
          <defaultValue>false</defaultValue>

specific language governing permissions and limitations
under the License.
-->

<project>
    <!-- once we move past supporting modelVersion 4.0.0 we should update this version -->
    <modelVersion>3.9.9</modelVersion>
    <groupId>tests.project</groupId>
    <artifactId>past-model-version</artifactId>
    <version>1</version>

    <exportedArtifact>org.eclipse.aether:aether-connector-basic</exportedArtifact>

    <!--
      | NOTE: Don't exclude the wagons or any of their dependencies (apart from the wagon API). This would otherwise
      | provoke linkage errors for wagons contributed by build extensions. We also don't need to exclude the wagons

  <description>
    Contains
    com.google.common.util.concurrent.internal.InternalFutureFailureAccess and
    InternalFutures. Most users will never need to use this artifact. Its
    classes are conceptually a part of Guava, but they're in this separate
    artifact so that Android libraries can use them without pulling in all of
    Guava (just as they can use ListenableFuture by depending on the
    listenablefuture artifact).