KIND, either express or implied.  See the License for the
specific language governing permissions and limitations
under the License.
-->

<project>
  <modelVersion>4.0.0</modelVersion>

  <groupId>org.apache.maven.its.mng3979</groupId>
  <artifactId>parent</artifactId>
  <version>0.1</version>
  <packaging>pom</packaging>

  <name>Maven Integration Test :: MNG-3979</name>
  <description>

  <modelVersion>4.0.0</modelVersion>

  <groupId>org.apache.maven.its.plugins</groupId>
  <artifactId>maven-it-plugin</artifactId>
  <version>0.1</version>
  <packaging>maven-plugin</packaging>

  <name>Maven Integration Test Plugin</name>
  <description>

KIND, either express or implied.  See the License for the
specific language governing permissions and limitations
under the License.
-->

<project>
  <modelVersion>4.0.0</modelVersion>

  <groupId>org.apache.maven.its.it0063</groupId>
  <artifactId>maven-it-it0063</artifactId>
  <version>1.0</version>
  <packaging>jar</packaging>

  <name>Maven Integration Test :: it0063</name>

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

<project>
  <modelVersion>4.0.0</modelVersion>

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

  <artifactId>child</artifactId>

  <name>Maven Integration Test :: MNG-3979</name>
  <description>

  <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

         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
  <modelVersion>4.0.0</modelVersion>

  <groupId>org.apache.maven.its.build.plugins</groupId>
  <artifactId>test</artifactId>
  <version>1.0</version>

  <name>MNG-7750</name>
  <description>
    Test build plugin and execution interpolation.
  </description>

  <properties>

                <groupId>org.apache.maven.its</groupId>
                <artifactId>bom</artifactId>
                <version>0.1</version>
                <type>pom</type>
                <scope>import</scope>
            </dependency>
        </dependencies>
    </dependencyManagement>

    <dependencies>
        <dependency>
            <groupId>org.apache.maven.its</groupId>
            <artifactId>a</artifactId>

under the License.
-->

<project>
  <modelVersion>4.0.0</modelVersion>
  <groupId>org.apache.maven.its.mng4034</groupId>
  <artifactId>parent</artifactId>
  <version>1.0-SNAPSHOT</version>
  <dependencies>
    <dependency>
      <groupId>org.apache.maven.its</groupId>
      <artifactId>maven-core-it-support</artifactId>
      <version>1.3</version>
      <scope>runtime</scope>
      <exclusions>

         Module Metadata hides the dependency declared in `guava` from runtime
         configurations downstream, and GWT uses the runtime configuration for
         its builds. Thus, GWT doesn't get j2objc-annotations transitively, in
         contrast to the other deps of `guava`, which it does get transitively.
         (Arguably we should redeclare *all* the `guava` deps here.) -->
    <dependency>

KIND, either express or implied.  See the License for the
specific language governing permissions and limitations
under the License.
-->

<project>
  <modelVersion>4.0.0</modelVersion>

  <groupId>org.apache.maven.its.mng3845</groupId>
  <artifactId>parent</artifactId>
  <version>0.1</version>
  <packaging>pom</packaging>

  <name>Maven Integration Test :: MNG-3845</name>
  <description>