blob: 001709a774ba40fdc2162052ca53b7623651ea69 [file] [log] [blame]
<?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>
<modelVersion>4.0.0</modelVersion>
<groupId>org.apache.maven.its.mng4052</groupId>
<artifactId>parent</artifactId>
<version>0.1</version>
<packaging>pom</packaging>
<name>Maven Integration Test :: MNG-4052</name>
<description>
Test that the project builder properly detects and handles inter-model dependencies within a reactor
like a POM that imports another POM. To clarify, this is not about the kind of dependency where one
project needs another project's output for compilation/testing but about the case where one project's
effective model requires another project's model for its construction.
</description>
<modules>
<!--
NOTE: We intentionally list importing-pom before imported-pom here to check that the construction of their
effective models works regardless of the reversed top-sort as given the inter-model dependencies.
-->
<module>importing-pom</module>
<module>imported-pom</module>
</modules>
</project>