// ArtifactId may differ only for multi-module projects, in which case
        // it must match the module name from a source root in modular sources.
        boolean isMultiModule = false;
        boolean validArtifactId = Objects.equals(a1, a2);
        for (SourceRoot sr : getSourceRoots(project)) {
            Optional<String> moduleName = sr.module();
            if (moduleName.isPresent()) {

    </module>
    <module name="RegexpSingleline">
        <property name="format" value="File \| Settings \| File Templates"/>
    </module>
    <module name="RegexpSingleline">
        <property name="format" value="Created with IntelliJ IDEA"/>
    </module>
    <module name="RegexpSingleline">
        <property name="format" value="^\s*\*\s*@author"/>
    </module>

            // Create module directory and POM
            Path moduleDir = tempDir.resolve("module1");
            Files.createDirectories(moduleDir);
            Path modulePom = moduleDir.resolve("pom.xml");
            String modulePomContent = PomBuilder.create()
                    .parent("com.example", "parent-project", "1.0.0")
                    .artifactId("module1")
                    .build();

  <artifactId>parent</artifactId>
  <version>11-SNAPSHOT</version>

  <name>Model urls inheritance test parent</name>
  <description>Flat directory structure case: module = ../child directory path + child directory path != child-artifact-id</description>

  <modules>
    <module>../inheritance</module><!-- current directory == inheritance -->
  </modules>

  <!-- 5 urls in the pom will be inherited with path added -->

     * Tests the formatting of an option with a module name.
     */
    @Test
    public void testModularOption() {
        String[] formatted = JavaPathType.patchModule("my.module").option(paths());
        assertEquals(2, formatted.length);
        assertEquals("--patch-module", formatted[0]);
        assertEquals(toPlatformSpecific("my.module=src/foo.java:src/bar.java"), formatted[1]);
    }

    /**

class DefaultGraphBuilderTest {
    /*
    The multi-module structure in this project is displayed as follows:

    module-parent
    └─── module-independent     (without parent declaration)
         module-a
         module-b               (depends on module-a)
         module-c
         └─── module-c-1
              module-c-2        (depends on module-b)
         module-d               (packaging is bom)
     */

  <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>

  <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>

## Decision

Organize the Gradle code base into a set of coarse-grained "architecture modules".
An architecture module is responsible for providing a coherent set of features and:

- Provides a set of APIs and services for use from outside the module.
- Has a private implementation.
- Is owned by a single team. A team may own multiple architecture modules.

The modules are arranged into several different "Gradle platforms".

## Composition by architecture modules

Each [architecture module and platform](platforms.md) can contribute code to any of the elements.
Not every module contributes to every element.