-->

        <!-- Imports -->
        <module name="RedundantImport"/>
        <module name="UnusedImports"/>
        <module name="IllegalImport">
            <!--
                We shouldn't use jdk.internal types.
                
                com.beust and org.testng.collections has classes that look like Guava.

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

<project>
  <modelVersion>4.0.0</modelVersion>

  <!--
  This minimalist POM tests mere inheritance from its parent. The <prerequisites> should not be inherited.
  -->

  <parent>
    <groupId>org.apache.maven.its.mng3843</groupId>
    <artifactId>parent-1</artifactId>
    <version>0.1</version>
  </parent>

  <artifactId>child-1</artifactId>

      </activation>
      <dependencies>
        <dependency>
          <groupId>org.apache.maven.its</groupId>
          <artifactId>maven-core-it-support</artifactId>
          <!-- version should be injected from dependency management of parent -->
        </dependency>
      </dependencies>
    </profile>
  </profiles>

          <required>true</required>
          <description>
            The Java type for this parameter. This is used to validate the result of any expressions used to calculate
            the value which should be injected into the Mojo for this parameter.
          </description>
        </field>
        <field>
          <name>required</name>
          <version>1.0.0+</version>
          <type>boolean</type>

  </description>

  <build>
    <!-- project extensions should precede inherited extensions -->
    <extensions>
      <extension>
        <groupId>org.apache.maven.its.mng3899</groupId>
        <artifactId>b</artifactId>
        <version>0.1</version>
      </extension>
      <extension>
        <!-- project extensions should override inherited extension with equal gid:aid -->

        <artifactId>maven-it-plugin-configuration</artifactId>
        <version>2.1-SNAPSHOT</version>
        <configuration>
          <!--
          All of these values should override the ones inherited from the parent. In particular, collections should not
          be merged with the values given by the parent POM.
          -->
          <propertiesFile>PASSED</propertiesFile>
          <stringParams>

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

<project>
    <modelVersion>4.999.999</modelVersion>
    <!-- this should be a fake "future" version that only has modelVersion understood by us -->
    <coordinates>tests.project:future-model-version</coordinates>

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

<project>
    <!-- once we move past supporting modelVersion 4.0.0 we should update this version -->
    <modelVersion>3.9.9</modelVersion>
    <groupId>tests.project</groupId>
    <artifactId>past-model-version</artifactId>
    <version>1</version>

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

<!--
NOTE: This POM's XML declaration specified no encoding which should therefore default to UTF-8.
-->

<project>
  <modelVersion>4.0.0</modelVersion>

  <groupId>org.apache.maven.its.mng2254</groupId>
  <artifactId>utf-8</artifactId>
  <version>0.1-SNAPSHOT</version>

                <!-- TODO(cpovirk): If we continue stripping these once we use @ElementTypesAreNonnullByDefault, then we should strip @ElementTypesAreNonnullByDefault, too, to reflect that the classes are *not* fully annotated. But hopefully we can stop stripping them, as https://github.com/jspecify/jspecify/issues/184 should make possible. -->
                <replace token="@Nullable" value="">
                  <fileset dir="${project.build.directory}">