<exclude name="**/testing/**"/>
</source>

<!--
    We used to set this only for packages that had manual supersource. That
    worked everywhere that I know of except for one place: when running the GWT
    util.concurrent tests under Guava.

    The problem is that GWT responds poorly to two .gwt.xml files in the same
    Java package; see https://goo.gl/pRV3Yn for details.

  <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
    plugin management and a profile are used.
  </description>

  <build>
    <!-- NOTE: This test used plugin management for the IT plugin -->
    <pluginManagement>
      <plugins>
        <plugin>

  <artifactId>maven-it-it0052</artifactId>
  <version>1.0</version>
  <packaging>jar</packaging>

  <name>Maven Integration Test :: it0052</name>
  <description>Test that source attachment doesn't take place when -DperformRelease=true is missing.</description>

  <!-- NOTE: Use stub versions of the core plugins referenced by the build -->
  <build>
    <pluginManagement>
      <plugins>
        <plugin>

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

  <name>Maven Integration Test :: MNG-2591</name>
  <description>
    Test aggregation of list configuration items for build plugins when using
    'combine.children=append' attribute.
  </description>

  <modules>
    <module>subproject</module>
  </modules>

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

    <commonsCliVersion>1.0</commonsCliVersion>
    <!--

    Do not update this, Doxia will be decoupled completely from 3.x and someone can
    create a rendering engine for it if they like when the release stabilizes. JVZ

    -->
    <doxiaVersion>1.0-alpha-9</doxiaVersion>
    <easyMockVersion>1.2_Java1.3</easyMockVersion>
    <junitVersion>4.13.1</junitVersion>

    <commonsCliVersion>1.0</commonsCliVersion>
    <!--

    Do not update this, Doxia will be decoupled completely from 3.x and someone can
    create a rendering engine for it if they like when the release stabilizes. JVZ

    -->
    <doxiaVersion>1.0-alpha-9</doxiaVersion>
    <easyMockVersion>1.2_Java1.3</easyMockVersion>
    <junitVersion>4.13.1</junitVersion>
    <plexusVersion>1.0-beta-3.0.7</plexusVersion>

   | This will determine whether maven prompts you when it needs input. If set to false,
   | maven will use a sensible default value, perhaps based on some other setting, for
   | the parameter in question.
   |
   | Default: true
  <interactiveMode>true</interactiveMode>
  -->

  <!-- offline
   | Determines whether maven should attempt to connect to the network when executing a build.

  <exclude name="**/testing/**"/>
</source>

<!--
    We used to set this only for packages that had manual supersource. That
    worked everywhere that I know of except for one place: when running the GWT
    util.concurrent tests under Guava.

    The problem is that GWT responds poorly to two .gwt.xml files in the same
    Java package; see https://goo.gl/pRV3Yn for details.

  <exclude name="**/testing/**"/>
</source>

<!--
    We used to set this only for packages that had manual supersource. That
    worked everywhere that I know of except for one place: when running the GWT
    util.concurrent tests under Guava.

    The problem is that GWT responds poorly to two .gwt.xml files in the same
    Java package; see https://goo.gl/pRV3Yn for details.

  <exclude name="**/testing/**"/>
</source>

<!--
    We used to set this only for packages that had manual supersource. That
    worked everywhere that I know of except for one place: when running the GWT
    util.concurrent tests under Guava.

    The problem is that GWT responds poorly to two .gwt.xml files in the same
    Java package; see https://goo.gl/pRV3Yn for details.