<name>aggregator</name>
          <version>1.0.0+</version>
          <type>boolean</type>
          <description>
            Flags this Mojo to run it in a multi-module way, i.e. aggregate the build with the set of projects
            listed as modules.
          </description>
          <defaultValue>false</defaultValue>
        </field>
        <field>
          <name>inheritedByDefault</name>

    </pluginManagement>
  </build>
  <modules>
    <module>maven-core</module>
    <module>apache-maven</module>
    <module>maven-model</module>
    <module>maven-plugin-api</module>
    <module>maven-project</module>
    <module>maven-reporting-api</module>
    <module>maven-project-builder</module>
    <module>maven-mercury</module>
    <module>maven-embedder</module>
    <module>maven-toolchain</module>

      <artifactId>cargo-core-api-generic</artifactId>
      <version>0.9</version>
      <scope>test</scope>
    </dependency>
    <dependency>
      <groupId>org.codehaus.cargo</groupId>
      <artifactId>cargo-core-api-module</artifactId>
      <version>0.9</version>
      <scope>test</scope>
    </dependency>
    <dependency>
      <groupId>org.codehaus.cargo</groupId>
      <artifactId>cargo-core-container-jetty</artifactId>

    </pluginManagement>
  </build>
  <modules>
    <module>maven-core</module>
    <module>apache-maven</module>
    <module>maven-model</module>
    <module>maven-plugin-api</module>
    <module>maven-project</module>
    <module>maven-reporting-api</module>
    <module>maven-project-builder</module>
    <module>maven-mercury</module>
    <module>maven-embedder</module>
    <module>maven-toolchain</module>

    </pluginManagement>
  </build>
  <modules>
    <module>maven-core</module>
    <module>apache-maven</module>
    <module>maven-model</module>
    <module>maven-plugin-api</module>
    <module>maven-project</module>
    <module>maven-reporting-api</module>
    <module>maven-project-builder</module>
    <module>maven-mercury</module>
    <module>maven-embedder</module>
    <module>maven-toolchain</module>

            .java files in c.g.c.collect.Collect, a module that the c.g.c.base test module inherits,
            and .java files in c.g.c.collect.testModule, one that it doesn't[*]. Consequently,
            c.g.c.base.testModule transitively pulls in .java files from both modules while reading
            the module description of only the prod module. And the prod module doesn't inherit all
            the modules that the test module classes use, so we get errors.

								<group>opensearch</group>
							</mapper>
						</data>
						<!-- Add elasicsearch modules directory -->
						<data>
							<type>directory</type>
							<src>${project.basedir}/modules</src>
							<mapper>
								<type>perm</type>
								<prefix>${packaging.fess.home.dir}/es/modules</prefix>
								<user>${packaging.fess.user}</user>
								<group>${packaging.fess.group}</group>
							</mapper>

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