<modelVersion>4.0.0</modelVersion>

  <groupId>cyclic-reference</groupId>
  <artifactId>parent</artifactId>
  <version>1.0-SNAPSHOT</version>
  <packaging>pom</packaging>

  <modules>
    <module>module-a</module>
    <module>module-b</module>
  </modules>

     * This method returns one of the values specified in the given collection.
     * This method does not handle the patch-module paths, because the patches
     * depend on which modules have been previously added on the module-paths.
     *
     * <p>If the dependency can be a constituent of both the class-path and the module-path,
     * then the path type is determined by checking if the dependency is modular.</p>
     *

setattr(_current_module, "keras", _KerasLazyLoader(globals(), mode="v1"))
_module_dir = _module_util.get_parent_dir_for_name("keras._tf_keras.keras")
_current_module.__path__ = [_module_dir] + _current_module.__path__
if _tf_uses_legacy_keras:
  _module_dir = _module_util.get_parent_dir_for_name("tf_keras.api._v1.keras")
else:
  _module_dir = _module_util.get_parent_dir_for_name("keras.api._v1.keras")

    <groupId>org.apache.maven.ut</groupId>
    <artifactId>parent</artifactId>
    <version>1.0-SNAPSHOT</version>
    <packaging>pom</packaging>
    <modules>
        <module>dep</module>
        <module>consumer</module>
    </modules>

     * Java does not accept the placement of two modules of the same name on the module-path.
     * So the modular test output directory usually needs to be placed in a {@code --path-module} option.
     *
     * <ul>
     *   <li>If the test output directory is modular, then:
     *     <ul>
     *       <li>If a test module name is identical to a main module name,

        override fun afterInvalidation(modules: Set<KtModule>) {
            modules.forEach { analysisSessionProvider.cache.remove(it) }
        }

        override fun afterGlobalInvalidation() {
            // Session invalidation events currently don't report whether library modules were included in the global invalidation. This is

  <groupId>lifecycle-participant-reactor-dependency-injection</groupId>
  <artifactId>parent</artifactId>
  <version>1.0</version>
  <packaging>pom</packaging>

  <modules>
    <module>module-a</module>
    <module>module-b</module>
  </modules>

        <artifactId>maven-test-a</artifactId>
        <version>1.0</version>
      </dependency>
    </dependencies>
  </dependencyManagement>
  <modules>
    <module>p1</module>
    <module>p2</module>
    <module>p3</module>
    <module>p4</module>
  </modules>

    <module>plexus-ircbot</module>
    <module>plexus-jdo</module>
    <module>plexus-jetty-httpd</module>
    <module>plexus-jetty</module>
    <module>plexus-mimetyper</module>
    <module>plexus-notification</module>
    <module>plexus-resource</module>
    <module>plexus-security</module>
    <module>plexus-summit</module>
    <module>plexus-taskqueue</module>
    <module>plexus-velocity</module>
    <module>plexus-xmlrpc</module>

      <roles>
        <role>Developer</role>
      </roles>
    </developer>
  </developers>

  <modules>
    <module>hamcrest-core</module>
    <module>hamcrest-generator</module>
    <module>hamcrest-library</module>
    <module>hamcrest-integration</module>
  </modules>