<modelVersion>4.0.0</modelVersion>

  <parent>
    <groupId>org.apache.maven</groupId>
    <artifactId>maven-compat-modules</artifactId>
    <version>4.1.0-SNAPSHOT</version>
  </parent>

  <artifactId>maven-toolchain-model</artifactId>

  <name>Maven Toolchain Model</name>
  <description>Maven Toolchain model.</description>

  <modelVersion>4.0.0</modelVersion>

  <parent>
    <groupId>org.apache.maven</groupId>
    <artifactId>maven-compat-modules</artifactId>
    <version>4.1.0-SNAPSHOT</version>
  </parent>

  <artifactId>maven-repository-metadata</artifactId>

  <name>Maven Repository Metadata Model</name>

#
# Controls caching behavior for different request types during Maven builds.
# Format: RequestType { scope:SCOPE ref:REFERENCE_TYPE }
#
# SCOPE OPTIONS:
#   session - Cache for entire Maven session (all modules in multi-module build)
#   request - Cache only for current request + its child requests
#   none    - Disable caching entirely
#
# REFERENCE OPTIONS:
#   hard - Strong reference (stays in memory, faster access)

                  <project path="$PROJECT_DIR$/build-logic/buildquality" />
                  <project path="$PROJECT_DIR$/build-logic/cleanup" />
                  <project path="$PROJECT_DIR$/build-logic/dependency-modules" />
                  <project path="$PROJECT_DIR$/build-logic/documentation" />
                  <project path="$PROJECT_DIR$/build-logic/idea" />
                  <project path="$PROJECT_DIR$/build-logic/integration-testing" />

        afterEvaluate {
          // This afterEvaluate hooks is required to avoid deprecated configuration resolution
          // This configuration can be removed once system modules are available
          def extraFipsJars = configurations.detachedConfiguration(bcFips, bcTlsFips)
          testClusters.configureEach {
            extraFipsJars.files.each {
              extraJarFile it
            }

The project state is managed by the `ProjectState` class.
It is created for each project in the build definition, once per build execution and is discarded at the end of the execution.

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

  <modelVersion>4.0.0</modelVersion>

  <parent>
    <groupId>org.apache.maven</groupId>
    <artifactId>maven-compat-modules</artifactId>
    <version>4.1.0-SNAPSHOT</version>
  </parent>

  <artifactId>maven-settings</artifactId>

  <name>Maven Settings</name>
  <description>Maven Settings model.</description>

  <dependencies>

     *   where multiple modules in the reactor have the same artifactId.
     * <p>
     * {@code -rf :artifactId} will pick up the first module which matches, but when multiple modules in the reactor
     *   have the same artifactId, effective failed module might be later in build reactor.
     * This means that developer will either have to type groupId or wait for build execution of all modules which

    /**
     * If the module path contains at least one filename-based auto-module, prepares a warning message.
     * The module path is the collection of dependencies associated with {@link JavaPathType#MODULES}.
     * It is caller's responsibility to send the message to a logger.
     *
     * @return warning message if at least one filename-based auto-module was found
     */

    }

    /**
     * Performs a lookup using Plexus API to make sure we can look up only "visible" (see Maven classloading) components
     * from current module and for example not extensions coming from other modules.
     */
    private LifecycleMapping lookupLifecycleMapping(final String packaging) {
        return lookup.lookupOptional(LifecycleMapping.class, packaging).orElse(null);
    }