<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>

        setResolved(true);
    }

    public MavenProject getProject() {
        return project;
    }

    @Override
    public List<Dependency> getDependencies() {
        return project.getModel().getDependencies();
    }

    @Override
    public List<Dependency> getManagedDependencies() {
        DependencyManagement depMngt = project.getModel().getDependencyManagement();

     * Whether the artifact should be added to the classpath depends on other
     * dependency properties.
     *
     * @return if the artifact can be added to the class path
     *
     * @deprecated A value of {@code true} does not mean that the dependency should
     * be placed on the classpath. See {@code JavaPathType} instead for better analysis.
     */
    @Deprecated

  <organization>
    <name>Codehaus</name>
  </organization>

  <dependencyManagement>

    <dependencies>

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

    </dependencies>

  </dependencyManagement>

      <url>file://dummy</url>
    </repository>
  </repositories>
  <dependencies>
    <dependency>
      <groupId>maven-test</groupId>
      <artifactId>t05-b</artifactId>
      <version>1.0</version>
      <type>jar</type>
      <scope>compile</scope>
    </dependency>
  </dependencies>

     *
     * <h4>Context-sensitive interpretation</h4>
     * A dependency with this path type will not necessarily be placed on the class path.
     * There are two circumstances where the dependency may nevertheless be placed somewhere else:
     *
     * <ul>
     *   <li>If {@link #MODULES} path type is also set, then the dependency can be placed either on the

      <name>Fake Maven Central Repository</name>
      <url>file://dummy</url>
    </repository>
  </repositories>
  <dependencies>
    <dependency>
      <groupId>maven-test</groupId>
      <artifactId>t04-b</artifactId>
      <version>2.0</version>
    </dependency>
  </dependencies>

      <url>file://dummy</url>
    </repository>
  </repositories>

  <dependencies>
    <dependency>
      <groupId>maven-test</groupId>
      <artifactId>t09-b</artifactId>
      <version>1.0</version>
      <scope>compile</scope>
    </dependency>
  </dependencies>

      <url>file://dummy</url>
    </repository>
  </repositories>

  <dependencies>
    <dependency>
      <groupId>maven-test</groupId>
      <artifactId>t10-b</artifactId>
      <version>1.0</version>
      <scope>compile</scope>
    </dependency>
  </dependencies>

      <url>file://dummy</url>
    </repository>
  </repositories>
  <dependencies>
    <dependency>
      <groupId>maven-test</groupId>
      <artifactId>maven-test-b</artifactId>
      <version>1.0</version>
      <type>jar</type>
      <scope>compile</scope>
    </dependency>
  </dependencies>