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

  <artifactId>child-artifact-id</artifactId>
  <name>Model inheritance test parent: module directory != artifactId</name>
  <description>
    artifactId == "child-artifact-id"
    but expect path on SCM and site == "child"

                    <version>1.0</version>
                    <packaging>pom</packaging>

                    <modules>
                        <module>child1</module>
                        <module>child2</module>
                    </modules>
                </project>
                """);

            // Create child1 with specific repository

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

        @Override
        public void afterProjectsRead(MavenSession session) {
            injectReactorDependency(session.getProjects(), "module-a", "module-b");
        }

        private void injectReactorDependency(List<MavenProject> projects, String moduleFrom, String moduleTo) {
            for (MavenProject project : projects) {
                if (moduleFrom.equals(project.getArtifactId())) {

    Source (English):

        «««
        "Hello world"
        “Hello Universe”
        "He said: 'Hello'"
        "The module is `__main__`"
        »»»

    Result (French):

        «««
        «Hello world»
        «Hello Universe»
        «He said: 'Hello'»
        «The module is `__main__`»
        »»»

### Ellipsis

- **Rules**: Content processing rules and validation

## Building and Testing

### Build Commands

```bash
# Build all modules
mvn clean install

# Build without tests
mvn clean install -DskipTests

# Build specific module
mvn clean install -pl fess-crawler

# Generate test coverage report
mvn jacoco:report
```

### Code Quality

```bash
# Format code

--------------------

Building your native images with [GraalVM] should work automatically.

See the okcurl module for an example build.

```shell
$ ./gradlew okcurl:nativeImage
$ ./okcurl/build/graal/okcurl https://httpbin.org/get
```

Java Modules
------------

OkHttp (5.2+) implements Java 9 Modules.

With this in place Java builds should fail if apps attempt to use internal packages.

```

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

        <executions>
          <execution>
            <id>attach-gradle-module-metadata</id>
            <goals>
              <goal>attach-artifact</goal>
            </goals>
            <configuration>
              <artifacts>
                <artifact>
                  <file>target/publish/module.json</file>
                  <type>module</type>
                </artifact>
              </artifacts>

    // Ignore warnings about using 'requires transitive' on automatic modules.
    // not needed when compiling with recent JDKs, e.g. 17
    options.compilerArgs.add("-Xlint:-requires-transitive-automatic")

    // Patch the compileKotlinJvm output classes into the compilation so exporting packages works correctly.
    options.compilerArgs.addAll(
      listOf(
        "--patch-module",