<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>
      <plugin>
        <groupId>org.apache.maven.its.plugins</groupId>

  <name>Maven Integration Test :: MNG-2174</name>
  <description>
    Verify that plugin dependencies defined by plugin management of a parent profile are not lost when the
    parent's main plugin management section is also present.
  </description>

  <modules>
    <module>sub</module>
  </modules>

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

  <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 uses plugin management for the test plugin -->
    <pluginManagement>
      <plugins>
        <plugin>

  <name>Maven Integration Test :: MNG-2174</name>
  <description>
    Verify that plugin dependencies defined by plugin management of a parent profile are not lost when the
    parent's main plugin management section is also present.
  </description>

  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.its.plugins</groupId>
        <artifactId>maven-it-plugin-class-loader</artifactId>
        <executions>

  <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>
      <id>pom-a</id>
      <properties>
        <pomProperty>a</pomProperty>
      </properties>
    </profile>
    <profile>
      <id>pom-b</id>
      <properties>

            <sourceFileExclude>**/ForceGuavaCompilation*</sourceFileExclude>
          </sourceFileExcludes>
          <!-- The above exclusion doesn't actually matter unless I prevent Javadoc from autodiscovering the source in the sourcepath, which defaults to the source directory :\ Boo for -sourcepath. -->
          <sourcepath>doesnotexist</sourcepath>

          </description>
          <association>
            <type>RepositoryPolicy</type>
          </association>
        </field>
      </fields>
      <!-- prevent Modello generation of an incorrect equals method. Could be avoided by using <identity/> tags to mark ID as the only identity field -->
      <codeSegments>
        <codeSegment>
          <version>1.0.0/1.1.0</version>

          <association>
            <type>RepositoryPolicy</type>
          </association>
        </field>
      </fields>
      <!-- prevent modello generation of an incorrect equals method. Could be avoided by using <identity/> tags to mark ID as the only identity field -->
      <codeSegments>
        <codeSegment>
          <version>1.0.0</version>

        </field>
        <field>
          <name>snapshotVersions</name>
          <version>1.1.0+</version>
          <description>Information for each sub-artifact available in this artifact snapshot. This is only the most recent SNAPSHOT for each unique extension/classifier combination.</description>
          <association>
            <type>SnapshotVersion</type>
            <multiplicity>*</multiplicity>
          </association>

          pages.

          This flag does not exist on 9-10 and 13+ (https://bugs.openjdk.java.net/browse/JDK-8215582).

          Consider removing it once our release and test scripts are migrated to a recent JDK (17+).
       -->
      <id>javadocs-jdk11-12</id>
      <activation>
        <jdk>[11,13)</jdk>
      </activation>
      <properties>