<groupId>maven-test</groupId>
  <artifactId>scope-test</artifactId>
  <version>1.0</version>
  <dependencies>

    <dependency>
      <groupId>maven-test-test</groupId>
      <artifactId>scope-default</artifactId>
      <version>1.0</version>
    </dependency>

    <dependency>
      <groupId>maven-test-test</groupId>
      <artifactId>scope-test</artifactId>
      <version>1.0</version>

<project>
  <modelVersion>4.0.0</modelVersion>
  <groupId>maven-test</groupId>
  <artifactId>maven-test-c</artifactId>
  <packaging>jar</packaging>
  <version>1.0</version>
  <dependencies>
    <dependency>
      <groupId>maven-test</groupId>
      <artifactId>maven-test-d</artifactId>
      <version>1.2</version>
      <type>jar</type>
      <scope>compile</scope>
    </dependency>
  </dependencies>

<project>
  <modelVersion>4.0.0</modelVersion>
  <groupId>maven-test</groupId>
  <artifactId>maven-test-d</artifactId>
  <packaging>jar</packaging>
  <version>1.1</version>

<project>
  <modelVersion>4.0.0</modelVersion>
  <groupId>maven-test</groupId>
  <artifactId>maven-test-d</artifactId>
  <packaging>jar</packaging>
  <version>1.1</version>

    public NearestConflictResolverTest() throws Exception {
        super("nearest");
    }

    // tests ------------------------------------------------------------------

    /**
     * Tests that <code>a:1.0</code> wins in the scenario:
     * <pre>
     * a:1.0
     * b:1.0 -&gt; a:2.0
     * </pre>
     */
    @Test
    void testDepth() {
        ResolutionNode a1n = createResolutionNode(a1);

  <modelVersion>4.0.0</modelVersion>
  <groupId>org.apache.maven.core.test</groupId>
  <artifactId>test-lifecycle-and-artifactHandler</artifactId>
  <packaging>jar</packaging>
  <version>1</version>
  <name>test-lifecycle-and-artifactHandler</name>

  <build>
    <plugins>
      <plugin>
        <artifactId>maven-assembly-plugin</artifactId>

     * So the modular test output directory usually needs to be placed in a {@code --path-module} option.
     *
     * <ul>
     *   <li>If the test output directory is modular, then:
     *     <ul>
     *       <li>If a test module name is identical to a main module name,
     *           place the test directory in a {@code --patch-module} option.</li>

 */
package org.apache.maven.artifact.resolver.filter;

import java.util.Arrays;

import org.junit.jupiter.api.Test;

import static org.junit.jupiter.api.Assertions.assertEquals;
import static org.junit.jupiter.api.Assertions.assertFalse;
import static org.junit.jupiter.api.Assertions.assertTrue;

/**
 * Tests {@link OrArtifactFilter}.
 *
 */
@Deprecated
class OrArtifactFilterTest {

import org.apache.maven.settings.v4.SettingsStaxReader;
import org.junit.jupiter.api.Test;

import static org.junit.jupiter.api.Assertions.assertTrue;

/**
 * Tests that the global settings.xml shipped with the distribution is in good state.
 *
 */
class GlobalSettingsTest {

    @Test
    void testValidGlobalSettings() throws Exception {

  <groupId>org.apache.maven.its.mng4053</groupId>
  <artifactId>test1</artifactId>
  <version>1.0-SNAPSHOT</version>

  <name>Maven Integration Test :: MNG-4053</name>
  <description>
    Verify that attributes in plugin configuration elements are not erroneously duplicated to other elements when
    no plugin management is used.
  </description>

  <build>
    <!-- NOTE: This test does not use plugin management for the IT plugin -->