<version>1.0</version>
  <packaging>pom</packaging>
  <modules>
    <module>module-2</module>
    <module>module-1</module>
    <module>module-3</module>
  </modules>
  <profiles>
    <profile>
      <id>a</id>
      <properties>
        <b>test-prop</b>
      </properties>
      <modules>
        <module>module-1</module>
        <module>module-4</module>
      </modules>
    </profile>
  </profiles>

        // JUnit has an "Automatic-Module-Name", so it appears on the module path.
        Map<PathType, List<Path>> dispatched = session.resolveDependencies(
                coord, PathScope.TEST_COMPILE, Arrays.asList(JavaPathType.CLASSES, JavaPathType.MODULES));
        List<Path> classes = dispatched.get(JavaPathType.CLASSES);
        List<Path> modules = dispatched.get(JavaPathType.MODULES);

     */
    private static final String MODULE_INFO = "module-info.class";

    /**
     * The attribute for automatic module name in {@code META-INF/MANIFEST.MF} files.
     */
    private static final Attributes.Name AUTO_MODULE_NAME = new Attributes.Name("Automatic-Module-Name");

    /**
     * Module information for the path specified at construction time.

  <modelVersion>4.0.0</modelVersion>
  <groupId>example.eclipse-548652</groupId>
  <artifactId>parent</artifactId>
  <version>0.0.1-SNAPSHOT</version>
  <packaging>pom</packaging>
  <modules>
    <module>child</module>
  </modules>

        assertEquals(project1.getScm().getUrl(), project0.getScm().getUrl() + "/modules/p1");
        assertEquals(project1.getScm().getConnection(), project0.getScm().getConnection() + "/modules/p1");
        assertEquals(
                project1.getScm().getDeveloperConnection(), project0.getScm().getDeveloperConnection() + "/modules/p1");
    }

    @Test

     * This method returns one of the values specified in the given collection.
     * This method does not handle the patch-module paths, because the patches
     * depend on which modules have been previously added on the module-paths.
     *
     * <p>If the dependency can be a constituent of both the class-path and the module-path,
     * then the path type is determined by checking if the dependency is modular.</p>
     *

  <scm>
    <connection>scm:svn:http://host/p0</connection>
    <developerConnection>scm:svn:https://host/p0</developerConnection>
    <url>http://host/viewer?path=/p0</url>
  </scm>

  <modules>
    <module>modules/p1</module>
  </modules>

  <packaging>pom</packaging>

  <name>Maven Integration Test :: MNG-3023</name>
  <description>Test that reactor projects are included in dependency resolution.</description>

  <modules>
    <module>dependency</module>
    <module>consumer</module>
  </modules>

     * This method returns one of the values specified in the given collection.
     * This method does not handle the patch-module paths, because the patches
     * depend on which modules have been previously added on the module-paths.
     *
     * <p>If the dependency can be a constituent of both the class-path and the module-path,
     * then the path type is determined by checking if the dependency is modular.</p>
     *

  <artifactId>plexus-containers</artifactId>
  <packaging>pom</packaging>
  <name>Parent Plexus Container POM</name>
  <version>1.0-alpha-16</version>
  <modules>
    <module>plexus-component-api</module>
    <module>plexus-container-default</module>
  </modules>
  <scm>
    <connection>scm:svn:http://svn.codehaus.org/plexus/plexus-containers/tags/plexus-containers-1.0-alpha-16</connection>