<?xml version="1.0" encoding="UTF-8"?>

<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements.  See the NOTICE file
distributed with this work for additional information
regarding copyright ownership.  The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License.  You may obtain a copy of the License at

  http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied.  See the License for the
specific language governing permissions and limitations
under the License.
-->

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
  <modelVersion>4.0.0</modelVersion>

  <groupId>org.apache.maven.its.mng2921</groupId>
  <artifactId>parent</artifactId>
  <version>1.0-SNAPSHOT</version>
  <packaging>pom</packaging>

  <name>Maven Integration Test :: MNG-2921 :: Parent</name> 
  <description>
    Verify that attached project artifacts can be resolved from the reactor as active project artifacts for
    consumption on other module's class paths. Note the subtle difference of this test compared to the closely
    related issue MNG-2871: This test is about *attached* artifacts, i.e. dependencies that have already been
    packaged. MNG-2871 on the other hand is about dependencies that haven't been packaged yet but merely exist
    as loose class files in a module's output directory.
  </description>

  <modules>
    <module>tests</module>
    <module>ejbs</module>
    <module>producer</module>
    <module>consumer</module>
  </modules>

</project>