// load the child project, which inherits from p0...
        MavenProject project0 = getProject(pom0);
        MavenProject project1 = getProject(pom1);

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

 * the {@code /project/modules/module} elements of the POM in the aggregator project.
 * Note that the aggregator project is required to have a {@code pom} packaging.</p>
 *
 * <p><dfn>Project inheritance</dfn> defines a parent-child relationship between projects.
 * The <dfn>child project</dfn> inherits all the information from the <dfn>parent project</dfn>
 * POM.</p>
 *
 */

         *   <li>In standard Maven project locations relative to the specified path</li>
         * </ul>
         *
         * @param project the path to search for a POM file
         * @return the path to the located POM file, or null if no POM can be found
         * @throws NullPointerException if project is null
         */
        @Nullable
        Path locateExistingPom(@Nonnull Path project);
    }

    /**

        File pom1 = new File(pom0Basedir, "p1/pom.xml");

        // load the child project, which inherits from p0...
        MavenProject project0 = getProjectWithDependencies(pom0);
        MavenProject project1 = getProjectWithDependencies(pom1);

        assertEquals(pom0Basedir, project1.getParent().getBasedir());
        assertNull(
                project1.getArtifact().getScope(),

        File pom1 = new File(pom0Basedir, "p1/pom.xml");

        // load everything...
        MavenProject project0 = getProjectWithDependencies(pom0);
        MavenProject project1 = getProjectWithDependencies(pom1);

        assertEquals(pom0Basedir, project1.getParent().getBasedir());
        Set set = project1.getArtifacts();
        assertNotNull(set, "No artifacts");
        assertFalse(set.isEmpty(), "No Artifacts");

 * </ol>
 * By understanding and properly configuring repositories, developers can control where Maven looks for dependencies, manage access to proprietary artifacts, and optimize the build process to ensure consistency and reliability across projects.
 *
 * @since 4.0.0
 * @see RemoteRepository
 * @see LocalRepository
 */

 * </ol>
 * <p>By understanding and properly configuring repositories, developers can control where Maven looks for dependencies, manage access to proprietary artifacts, and optimize the build process to ensure consistency and reliability across projects.
 * </p>
 *
 *
 * @since 4.0.0
 * @see Repository
 * @see LocalRepository

 * **Be pragmatic**: Questions are encouraged and should be asked early in the process to avoid
   problems later. Be thoughtful and considerate when seeking out the appropriate forum for your
   questions. Those who are asked should be responsive and helpful.

 * **Step down considerately**: Members of every project come and go. When somebody leaves or
   disengages from the project, they should make it known and take the proper steps to ensure that

Unlike many projects on GitHub, the Go project does not use its bug tracker for general discussion or asking questions.
We only use our bug tracker for tracking bugs and tracking proposals going through the [Proposal Process](https://go.dev/s/proposal-process).

For asking questions, see:

* [The golang-nuts mailing list](https://groups.google.com/d/forum/golang-nuts)

* [The Go Forum](https://forum.golangbridge.org/), a web-based forum

    Optional<Boolean> resume();

    /**
     * Returns the project to resume the build from.
     *
     * @return an {@link Optional} containing the project name to resume from, or empty if not specified
     */
    @Nonnull
    Optional<String> resumeFrom();

    /**
     * Returns the list of specified reactor projects to build instead of all projects.
     *