<ciManagement>
    <system>GitHub Actions</system>
    <url>https://github.com/google/guava/actions</url>
  </ciManagement>
  <modules>
    <module>guava</module>
    <module>guava-bom</module>
    <module>guava-gwt</module>
    <module>guava-testlib</module>
    <module>guava-tests</module>
  </modules>
  <build>
    <!-- Handle where Guava deviates from Maven defaults -->
    <sourceDirectory>src</sourceDirectory>

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

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

  </developers>
  <ciManagement>
    <system>GitHub Actions</system>
    <url>https://github.com/google/guava/actions</url>
  </ciManagement>
  <modules>
    <module>guava</module>
    <module>guava-bom</module>
    <module>guava-testlib</module>
    <module>guava-tests</module>
  </modules>
  <build>
    <!-- Handle where Guava deviates from Maven defaults -->
    <sourceDirectory>src</sourceDirectory>

    Map<Dependency, Path> getDependencies();

    /**
     * Returns the Java module name of the dependency at the given path.
     * The given dependency should be one of the paths returned by {@link #getDependencies()}.
     * The module name is extracted from the {@code module-info.class} file if present, otherwise from
     * the {@code "Automatic-Module-Name"} attribute of the {@code META-INF/MANIFEST.MF} file if present.
     *

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

    // Ensure we start from scratch.
    fileSystem.deleteRecursively(workspaceDir)
    fileSystem.createDirectories(workspaceDir)
  }

  /**
   * Resolve the OSGi metadata of the all okhttp3 modules. If required modules do not have OSGi
   * metadata this will fail with an exception.
   */
  @Test
  fun testMainModuleWithSiblings() {
    createWorkspace().use { workspace ->
      createBndRun(workspace).use { bndRun ->

 * conventions. Both binary and source-incompatible changes are possible, including complete removal
 * of the experimental API.
 *
 * Do not use these APIs in modules that may be executed using a version of OkHttp different from
 * the version the module was compiled with.
 *
 * Do not use these APIs in published libraries.
 *
 * Do not use these APIs if you aren't willing to track changes to them.
 */
@MustBeDocumented

// implementations compliant with FIPS 140.
//
// FIPS 140 [1] is a US standard for data processing that specifies
// requirements for cryptographic modules. Software that is "FIPS 140
// compliant" must use approved cryptographic primitives only and that
// are implemented by a FIPS 140 certified cryptographic module.
//
// So, FIPS 140 requires that a certified implementation of e.g. AES
// is used to implement more high-level cryptographic protocols.

        List<MavenProject> modules = requestPomProject.getCollectedProjects() != null
                ? requestPomProject.getCollectedProjects()
                : Collections.emptyList();

        List<MavenProject> result = new ArrayList<>(modules);
        result.add(requestPomProject);
        return result;
    }