<modelVersion>4.0.0</modelVersion>
  <groupId>com.example.group</groupId>
  <artifactId>testvalidpom</artifactId>
  <version>0.0.1-SNAPSHOT</version>

  <description>
    This will test if the module validator recognized that this dependency with classifier
    is not the same as the module itself.
  </description>
  <dependencies>
    <dependency>
      <groupId>com.example.group</groupId>
      <artifactId>testvalidpom</artifactId>

  <modelVersion>4.0.0</modelVersion>
  <groupId>com.example.group</groupId>
  <artifactId>testinvalidpom</artifactId>
  <version>0.0.1-SNAPSHOT</version>

  <description>
    This will test if the module validator recognized that this
    dependency is the same as the module itself.
  </description>
  <dependencies>
    <dependency>
      <groupId>com.example.group</groupId>
      <artifactId>testinvalidpom</artifactId>

        Artifact artifact;
        artifact = getArtifact(project, groupId, "scope-compile");
        assertEquals(scopeValue, artifact.getScope(), "Check scope");
        artifact = getArtifact(project, groupId, "scope-test");
        assertNull(artifact, "Check test dependency is not transitive");
        artifact = getArtifact(project, groupId, "scope-provided");

    <p>Per-directory repository metadata <code>repository-metadata.xml</code>.</p>
    <p>A directory may represent 3 types of content: "groupId", "groupId/artifactId" or "groupId/artifactId/version".</p>
    <p>Most metadata content has a meaning when the directory represents a "groupId/artifactId" (<code>groupId</code>, <code>artifactId</code>, <code>versioning</code>)<p>]]>
  </description>
  <defaults>
    <default>
      <key>package</key>

    <modelVersion>4.0.0</modelVersion>

    <groupId>test</groupId>
    <artifactId>other-import</artifactId>
    <version>0.1-SNAPSHOT</version>
    <packaging>pom</packaging>

    <dependencyManagement>
        <dependencies>
            <dependency>
                <groupId>test</groupId>
                <artifactId>mydep</artifactId>
                <version>0.3</version>

  <modelVersion>4.0.0</modelVersion>

  <parent>
    <groupId>cyclic-reference</groupId>
    <artifactId>parent</artifactId>
    <version>1.0-SNAPSHOT</version>
  </parent>
  <artifactId>module-b</artifactId>

  <dependencies>
    <dependency>
      <groupId>cyclic-reference</groupId>
      <artifactId>module-a</artifactId>
      <version>1.0-SNAPSHOT</version>
    </dependency>

            String pomContent = Files.readString(pomFile);
            assertTrue(
                    pomContent.contains("<groupId>com.example</groupId>"),
                    "Expected " + pomContent + " to contain " + "<groupId>com.example</groupId>");
            // Note: The exact modifications depend on which strategies are applicable
            // This test mainly verifies that apply goal can modify files

  <groupId>org.apache.maven.its.mng3586</groupId>
  <artifactId>test2</artifactId>
  <version>1.0</version>

  <name>Maven Integration Test :: MNG-3586</name>
  <description>
    Test that plugin dependencies with scope system are part of the plugin class realm.
  </description>

  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.its.plugins</groupId>

-->

<project>
  <modelVersion>4.0.0</modelVersion>
  <artifactId>aid</artifactId>
  <groupId>gid</groupId>
  <version>1.0</version>

  <build>
    <plugins>
      <plugin>
        <artifactId>maven-it-plugin</artifactId>
        <version>1.0</version>
        <dependencies>
          <dependency>
            <groupId>test</groupId>
            <!-- artifact id missing -->
            <version>2.0</version>

-->

<project>
  <modelVersion>4.0.0</modelVersion>
  <artifactId>aid</artifactId>
  <groupId>gid</groupId>
  <version>1.0</version>

  <build>
    <plugins>
      <plugin>
        <artifactId>maven-it-plugin</artifactId>
        <version>1.0</version>
        <dependencies>
          <dependency>
            <groupId>test</groupId>
            <artifactId>a</artifactId>
            <!-- version missing -->