modulesElement.name(SUBPROJECTS);
            context.detail("Converted <modules> to <subprojects>");

            // Convert all module children to subproject
            var moduleElements = modulesElement.children(MODULE).toList();
            for (Element moduleElement : moduleElements) {
                moduleElement.name(SUBPROJECT);
            }

        Path resolvedPath = Paths.get("/tmp/subproject/pom.xml");
        when(locator.locateExistingPom(any(Path.class))).thenReturn(resolvedPath);

        Sources.BuildPathSource source = (Sources.BuildPathSource) Sources.buildSource(basePath);
        ModelSource resolved = source.resolve(locator, "subproject");

        assertNotNull(resolved);

                        .map(subprojects -> {
                            DomUtils.removeElement(subprojects);
                            context.detail(
                                    "Removed: redundant subprojects list from profile (matches direct children)");
                            return true;
                        })
                        .orElse(false))

 * called the <dfn>aggregator project</dfn> lists one or more <dfn>sub-projects</dfn>
 * which are relative pointers on the file system to other projects. This is done using
 * the {@code /project/subprojects/subproject} elements of the POM in the aggregator project.
 * Note that the aggregator project is required to have a {@code pom} packaging.</p>
 *

            Element subprojects = DomUtils.findChildElement(root, "subprojects");
            assertNotNull(subprojects);

            // Verify module elements were renamed to subproject
            var moduleElements = subprojects.children("module").toList();
            var subprojectElements = subprojects.children("subproject").toList();
            assertEquals(0, moduleElements.size());

 *   <li><strong>Schema Location Update</strong>: Updates xsi:schemaLocation to Maven 4.1.0 XSD</li>
 *   <li><strong>Module Conversion</strong>: Converts {@code <modules>} to {@code <subprojects>} and {@code <module>} to {@code <subproject>}</li>
 *   <li><strong>Model Version Update</strong>: Updates {@code <modelVersion>} to 4.1.0</li>
 * </ol>
 *
 * <h3>Default Behavior</h3>

          </annotations>
        </field>
        <field xdoc.separator="blank">
          <name>subprojects</name>
          <version>4.1.0+</version>
          <description>The subprojects (formerly called modules) to build as a part of this
            project. Each subproject listed is a relative path to the directory containing the subproject.
            To be consistent with the way default URLs are calculated from parent, it is recommended

/** Configure building for Java+Kotlin projects. */
subprojects {
  val project = this@subprojects
  if (project.name == "okhttp-bom") return@subprojects

  if (project.name == "okhttp-android") return@subprojects
  if (project.name == "android-test") return@subprojects
  if (project.name == "regression-test") return@subprojects
  if (project.name == "android-test-app") return@subprojects
  if (project.name == "container-tests") return@subprojects

        Path locateExistingPom(@Nonnull Path project);
    }

    /**
     * Resolves a relative path to another POM file using the provided model locator.
     * This method is specifically used to locate POM files for subprojects or related
     * projects referenced from the current POM.
     *
     * <p>The resolution process typically involves:</p>
     * <ul>
     *   <li>Normalizing the relative path for the current platform</li>

        assertEquals(1, results.size());
        MavenProject parent = results.get(0).getProject();
        assertEquals("parent", parent.getArtifactId());
        // The subprojects list should be empty since we explicitly defined an empty <subprojects /> element
        assertTrue(parent.getModel().getDelegate().getSubprojects().isEmpty());
    }

    @Test