org.apache.maven.api.Toolchain rareToolchain = mock(org.apache.maven.api.Toolchain.class);
        when(toolchainFactoryRareType.createToolchain(any())).thenReturn(rareToolchain);

        List<Toolchain> toolchains = toolchainManager.getToolchains(session, "rare", null);

        assertEquals(1, toolchains.size());
    }

    @Test
    void testModelsAndFactory() {

     * @return the toolchain selected by <code>maven-toolchains-plugin</code>
     */
    Toolchain getToolchainFromBuildContext(String type, MavenSession context);

    /**
     * Select all toolchains available in user settings matching the type and requirements,
     * independently from <code>maven-toolchains-plugin</code>.
     *
     * @param session the Maven session, must not be {@code null}

import org.apache.maven.api.annotations.Nonnull;
import org.apache.maven.api.toolchain.PersistedToolchains;

/**
 *
 * @since 4.0.0
 */
@Experimental
public interface ToolchainsBuilderResult extends Result<ToolchainsBuilderRequest> {
    /**
     * Gets the assembled toolchains.
     *
     * @return the assembled toolchains, never {@code null}
     */
    @Nonnull
    PersistedToolchains getEffectiveToolchains();

          <groupId>org.mvnsearch</groupId>
          <artifactId>toolchains-maven-plugin</artifactId>
          <version>4.5.0</version>
          <executions>
            <!--
            We can apparently have only one <jdk> per execution: Others are silently ignored :(
            To properly test this, you need to remove existing toolchains:
            rm -rf ~/.m2/jdks/ ~/.m2/toolchains.xml

          <groupId>org.mvnsearch</groupId>
          <artifactId>toolchains-maven-plugin</artifactId>
          <version>4.5.0</version>
          <executions>
            <!--
            We can apparently have only one <jdk> per execution: Others are silently ignored :(
            To properly test this, you need to remove existing toolchains:
            rm -rf ~/.m2/jdks/ ~/.m2/toolchains.xml

// CHECKSTYLE_OFF: RegexpHeader
/**
 * Provides classes for managing Maven toolchains, which allow projects to use specific
 * tool installations (like JDKs, compilers, or other build tools) across different
 * environments without hardcoding paths.
 *
 * @since 4.0.0
 */

 -----
 2006-11-04
 -----

Maven 4 API - Immutable Toolchains Model

 This is strictly the immutable model for Maven toolchains in <<<org.apache.maven.api.toolchain>>> package.

 The following are generated from this model:

   * {{{./apidocs/index.html}Java sources}} with <<<Builder>>> inner classes for immutable instances creation.

 * under the License.
 */
package org.apache.maven.toolchain;

import org.apache.maven.execution.MavenSession;

/**
 * Component for use by the <code>maven-toolchains-plugin</code> only.
 * It provides API: <ol>
 * <li>to retrieve every toolchains available in user settings,</li>
 * <li>to store chosen toolchain into build context for later use by toolchain-aware plugins.</li>
 * </ol>
 *
 * @since 2.0.9

 * under the License.
 */
package org.apache.maven.toolchain;

import java.util.Map;

import org.apache.maven.toolchain.model.ToolchainModel;

/**
 * a private contract between the toolchains plugin and the components.
 *
 * @deprecated Use {@link org.apache.maven.api.Toolchain} instead.
 */
@Deprecated(since = "4.0.0")
public interface ToolchainPrivate extends Toolchain {

    /**

      </exclusions>
    </dependency>
  </dependencies>
  <build>
    <plugins>
      <plugin>
        <groupId>org.mvnsearch</groupId>
        <artifactId>toolchains-maven-plugin</artifactId>
      </plugin>
      <plugin>
        <artifactId>maven-toolchains-plugin</artifactId>
      </plugin>
      <plugin>
        <artifactId>maven-compiler-plugin</artifactId>
        <executions>
          <execution>