* by concurrently running mojo executions. To prevent race conditions, an aggregating execution will block
     * all other executions until finished.
     * We also lock on a given project to forbid a forked lifecycle to be executed concurrently with the project.
     * TODO: ideally, the builder should take care of the ordering in a smarter way

        msgs.add("* but aggregator Mojos require exclusive access to reactor to   *");
        msgs.add("* prevent race conditions. This mojo execution will be blocked  *");
        msgs.add("* until the aggregator work is done.                            *");
        msgs.add("*****************************************************************");

        assertEquals(
                msgs,

  </scm>
  <organization>
    <name>Codehaus</name>
    <url>http://www.codehaus.org/</url>
  </organization>
  <modules>
    <!--

    Until the bug is fixed in Maven which is pulling in the trunk to the
    appserver build.
    <module>plexus-appserver</module>
    -->
    <module>plexus-archetypes</module>
    <module>plexus-examples</module>

                        projectOs.reset();
                    }
                } while (!completedBuilds.contains(projectBuild));
            }
            running = false;
        }

        /*
        Wait until we are sure the print-stream thread is running.
         */

        public void waitUntilRunning(boolean expect) {
            while (!running == expect) {
                try {
                    Thread.sleep(10);

        <otherArchive>http://maven.commits.markmail.org/</otherArchive>
      </otherArchives>
    </mailingList>
    <!--
      duplication from parent pom - temporary until they inherit
      properly
    -->
    <mailingList>
      <name>Maven Announcements List</name>
      <post>******@****.***</post>
      <subscribe>******@****.***</subscribe>

        <otherArchive>http://maven.commits.markmail.org/</otherArchive>
      </otherArchives>
    </mailingList>
    <!--
      duplication from parent pom - temporary until they inherit
      properly
    -->
    <mailingList>
      <name>Maven Announcements List</name>
      <post>******@****.***</post>
      <subscribe>******@****.***</subscribe>

import org.apache.maven.settings.Server;
import org.eclipse.aether.RepositorySystemSession;

/**
 * @since 3.0-alpha
 * @deprecated Use {@link MavenRepositorySystem} if needed, or maven-resolver directly, until maven 4.x api is out
 */
@Deprecated
public interface RepositorySystem {
    String DEFAULT_LOCAL_REPO_ID = MavenRepositorySystem.DEFAULT_LOCAL_REPO_ID;

    @SuppressWarnings("checkstyle:constantname")

                            + repository.getUrl()
                            + " was cached in the local repository. "
                            + "Resolution will not be reattempted until the update interval of "
                            + repository.getId() + " has elapsed or updates are forced. Original error: " + error);

                } else {

  </scm>
  <organization>
    <name>Codehaus</name>
    <url>http://www.codehaus.org/</url>
  </organization>
  <modules>
    <!--

    Until the bug is fixed in Maven which is pulling in the trunk to the
    appserver build.
    <module>plexus-appserver</module>
    -->
    <module>plexus-archetypes</module>
    <module>plexus-examples</module>

    @Test
    void testRemoteResourcesPlugin() throws Exception {
        // TODO turn an equivalent back on when the RR plugin is released.

        /*

        This will not work until the RR plugin is released to get rid of the binding to the reporting exception which is a mistake.

        This happens after removing the reporting API from the core: