<description>
            Configuration for different proxy profiles. Multiple proxy profiles
            might come in handy for anyone working from a notebook or other
            mobile platform, to enable easy switching of entire proxy
            configurations by simply specifying the profile id, again either from
            the command line or from the defaults section below.
          </description>

     */
    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.

    <module>plexus-jdo</module>
    <module>plexus-jetty-httpd</module>
    <module>plexus-jetty</module>
    <module>plexus-mimetyper</module>
    <module>plexus-notification</module>
    <module>plexus-resource</module>
    <module>plexus-security</module>
    <module>plexus-summit</module>
    <module>plexus-taskqueue</module>
    <module>plexus-velocity</module>
    <module>plexus-xmlrpc</module>
  </modules>

     *       then the test dependency will be placed on the Java {@code --patch-module} option instead of the
     *       {@code --module-path} option.</li>
     * </ul>
     */
    MODULES("--module-path"),

    /**
     * The path identified by the Java {@code --upgrade-module-path} option.
     */
    UPGRADE_MODULES("--upgrade-module-path"),

    /**

  </build>
  <modules>
    <module>maven-archiver</module>
    <module>maven-artifact</module>
    <module>maven-artifact-manager</module>
    <module>maven-artifact-ant</module>
    <module>maven-artifact-test</module>
    <module>maven-core</module>
    <module>maven-error-diagnostics</module>
    <module>maven-model</module>
    <module>maven-monitor</module>
    <module>maven-plugin-api</module>

        request.setResumeFrom(":module-b");
        Properties properties = new Properties();
        properties.setProperty("remainingProjects", ":module-a");

        repository.applyResumptionProperties(request, properties);

        assertThat(request.getResumeFrom(), is(":module-b"));
    }

    @Test
    void projectsFromPropertyGetsAddedToExistingRequestParameters() {

  </organization>
  <modules>
    <module>plexus-appserver</module>
    <module>plexus-archetypes</module>
    <module>plexus-components</module>
    <module>plexus-component-factories</module>
    <module>plexus-containers</module>
    <module>plexus-logging</module>
    <module>plexus-maven-plugin</module>
    <module>plexus-services</module>
    <module>plexus-tools</module>
    <module>plexus-utils</module>

    appserver build.
    <module>plexus-appserver</module>
    -->
    <module>plexus-archetypes</module>
    <module>plexus-examples</module>
    <module>plexus-components</module>
    <module>plexus-component-factories</module>
    <module>plexus-containers</module>
    <module>plexus-logging</module>
    <module>plexus-maven-plugin</module>
    <module>plexus-tools</module>
    <module>plexus-utils</module>

  <modelVersion>4.0.0</modelVersion>

  <groupId>cyclic-reference</groupId>
  <artifactId>parent</artifactId>
  <version>1.0-SNAPSHOT</version>
  <packaging>pom</packaging>

  <modules>
    <module>module-a</module>
    <module>module-b</module>
  </modules>

      <roles>
        <role>Developer</role>
      </roles>
    </developer>
  </developers>

  <modules>
    <module>hamcrest-core</module>
    <module>hamcrest-generator</module>
    <module>hamcrest-library</module>
    <module>hamcrest-integration</module>
  </modules>