* @return file representing the tool executable, or null if the tool cannot be found
     */
    String findTool(String toolName);

    /**
     * Let the toolchain decide if it matches requirements defined
     * in the toolchain plugin configuration.
     * @param requirements Map<String, String> key value pair, may not be {@code null}

 ---
 Hervé Boutemy
 ---
 2013-08-02
 ---

Plugins Bindings for <<<default>>> Lifecycle Reference

  The {{{./lifecycles.html}<<<default>>> lifecycle}} is defined without any plugin binding; plugins bindings are defined separately
  in {{{./apidocs/org/apache/maven/lifecycle/providers/packaging/package-summary.html}<<<org.apache.maven.lifecycle.providers.packaging>>>}} package
  because they are specific for each packaging:

    public Map<String, Lifecycle> getPhaseToLifecycleMap() {
        // If people are going to make their own lifecycles then we need to tell people how to namespace them correctly
        // so that they don't interfere with internally defined lifecycles.

        Map<String, Lifecycle> phaseToLifecycleMap = new HashMap<>();

        for (Lifecycle lifecycle : getLifeCycles()) {
            logger.debug("Lifecycle {}", lifecycle);

 ---
 Maven Core Extensions Reference
 ---
 Hervé Boutemy
 ---
 2016-06-25
 ---

Maven Core Extensions Reference

  Maven core provides default {{{./extension.html}extensions}} as defined in <<</META-INF/maven/extension.xml>>>:

    String ROLE = GraphConflictResolver.class.getName();

    /**
     * Cleanses the supplied graph by leaving only one directed versioned edge\
     * between any two nodes, if multiple exists. Uses scope relationships, defined
     * in <code>ArtifactScopeEnum</code>
     *
     * @param graph the "dirty" graph to be simplified via conflict resolution
     * @param scope scope for which the graph should be resolved
     *

 *
 */
public class LifecyclePhaseNotFoundException extends Exception {

    private final String lifecyclePhase;

    /**
     * Creates a new exception to indicate that the specified lifecycle phase is not defined by any known lifecycle.
     *
     * @param message The detail message, may be {@code null}.
     * @param lifecyclePhase The name of the lifecycle phase that could not be located, may be {@code null}.
     */

  <name>Maven Integration Test :: MNG-4193</name>
  <description>
    Test that multiple artifact repository declarations with the same id cause a validation error even if the
    repositories are defined within a (non-active) profile.
  </description>

  <profiles>
    <profile>
      <id>test</id>
      <repositories>
        <repository>
          <id>one</id>

import org.apache.maven.artifact.versioning.OverConstrainedVersionException;

/**
 * Resolves conflicting artifacts by always selecting the newest declaration. Newest is defined as the
 * declaration whose version is greater according to <code>ArtifactVersion.compareTo</code>.
 *
 * @see ArtifactVersion#compareTo
 * @since 3.0
 */
@Named("newest")
@Singleton
@Deprecated

    @Inject
    public DefaultLifecycleProvider() {
        super(
                LIFECYCLE_ID,
                PHASES,
                null // no global plugin bindings for default lifecycle: they are defined per-packaging in separate
                // providers
                );
    }

  <name>Maven Integration Test :: MNG-4008</name>
  <description>
    Verify that filter definitions are properly merged.
  </description>

  <build>
    <filters>
      <!-- NOTE: The first filter is deliberately defined by the child as well, so should not be added twice -->
      <filter>src/main/filters/child-a.properties</filter>
      <filter>src/main/filters/parent-c.properties</filter>
      <filter>src/main/filters/parent-b.properties</filter>