* of project dependencies. This optimizes module loading during runtime, as we will only load external
 * modules that are not loaded transitively by other project modules.
 *
 * We perform this filtering, since if we simply include all external dependencies, regardless of whether
 * they are already loaded transitively, there is a measurable performance impact during module-loading.
 */

| <<<test-jar>>>        | <<<tests>>>   | <<<jar>>>  | java      | classes, patch module |                       |
*-----------------------+---------------+------------+-----------+-----------------------+-----------------------+
| <<<modular-jar>>> *   | <<<tests>>>   | <<<jar>>>  | java      | modules               |                       |

  <name>Model urls inheritance test parent</name>
  <description>MNG-5951 MNG-6059 child.x.y.inherit.append.path="false" for each url to avoid automatic path addition when inheriting</description>

  <modules>
    <module>../inheritance</module>
  </modules>

  <!-- 5 urls in the pom to configure for not adding path -->
  <url>http://www.apache.org/path/to/parent/</url>
  <scm child.scm.connection.inherit.append.path="false"

-->

<project>
  <modelVersion>4.0.0</modelVersion>
  <artifactId>foo</artifactId>
  <groupId>foo</groupId>
  <version>99.44</version>
  <packaging>bleh</packaging>

  <modules>
    <module>test-module</module>
  </modules>

        config-file: ./.github/codeql/codeql-config.yml

    - name: Cleanup Gradle Cache
      # Cleans up the Gradle caches before being cached
      run: |
        rm -f ~/.gradle/caches/modules-2/modules-2.lock
        rm -f ~/.gradle/caches/modules-2/gc.properties

			<excludes>
				<exclude>*</exclude>
			</excludes>
			<filtered>false</filtered>
		</fileSet>
		<!-- es/modules -->
		<fileSet>
			<directory>${project.basedir}/modules</directory>
			<outputDirectory>fess-${project.version}/es/modules</outputDirectory>
		</fileSet>
		<!-- es/plugins -->
		<fileSet>
			<directory>${project.basedir}/plugins</directory>

  <version>11-SNAPSHOT</version>

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

  <modules>
    <module>../inheritance</module>
  </modules>

  <!-- 5 urls in the pom will be inherited with path added -->
  <url>http://www.apache.org/path/to/parent/</url>
  <scm>

  <name>Model urls inheritance test parent</name>
  <description>Most classical case: child in direct subdirectory with directory name == child artifactId</description>

  <modules>
    <module>child-artifact-id</module>
  </modules>

  <!-- 5 urls in the pom will be inherited with path added -->
  <url>http://www.apache.org/path/to/parent/</url>
  <scm>
    <connection>scm:my-scm:http://domain.org/base</connection>

  <modelVersion>4.0.0</modelVersion>
  <groupId>inheritance</groupId>
  <artifactId>empty</artifactId>
  <version>1</version>
  <modules>
    <module>child</module>
  </modules>
  <url></url>
  <scm>
    <connection> </connection>
    <developerConnection>  </developerConnection>
    <url></url>
  </scm>
  <distributionManagement>
    <site>
      <url></url>

## Composition by architecture modules

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

The core-runtime module defines each runtime:

- The target JVM for the runtime. Each runtime has its own JVM compatibility constraints.