* under the License.
 */
package org.apache.maven.lifecycle.mapping;

import java.util.List;

import org.apache.maven.api.xml.XmlNode;
import org.apache.maven.model.Dependency;

/**
 * Mojo (plugin goal) binding to a lifecycle phase.
 *
 * @see LifecyclePhase
 */
public class LifecycleMojo {

    private String goal;
    private XmlNode configuration;
    private List<Dependency> dependencies;

                Set<Binding<Q>> res = getBindings(key);
                if (res != null && !res.isEmpty()) {
                    List<Binding<Q>> bindingList = new ArrayList<>(res);
                    Comparator<Binding<Q>> comparing = Comparator.comparing(Binding::getPriority);
                    bindingList.sort(comparing.reversed());
                    Binding<Q> binding = bindingList.get(0);

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

%{toc|fromDepth=2}

* <<<default>>> Lifecycle

  <<<default>>> lifecycle is defined only with phases, <<without>> any associated plugin binding:
  plugins bindings for this lifecycle are {{{./default-bindings.html}defined separately for each packaging}}:

          <role>org.apache.maven.plugin.loader.PluginLoader</role>
          <field-name>pluginLoader</field-name>
        </requirement>
        <requirement>
          <role>org.apache.maven.lifecycle.binding.MojoBindingFactory</role>
          <field-name>bindingFactory</field-name>
        </requirement>
      </requirements>
    </mojo>
  </mojos>

  mode.

** Maven-Core

  We'll examine the different parts of maven-core on a case-by-case
  basis, below:

*** DefaultLifecycleExecutor

  When binding goals to the project's configured lifecycle, each mojo
  descriptor should declare whether it requires online/offline status.
  This value should be a java.lang.Boolean, so it can implement 3VL

    //      only deal in concrete terms -- all version finding mumbo jumbo is a customization to base functionality
    //      the plugin manager provides.

    @Test
    void testRemoteResourcesPlugin() throws Exception {
        // TODO turn an equivalent back on when the RR plugin is released.

        /*

        This will not work until the RR plugin is released to get rid of the binding to the reporting exception which is a mistake.

 * the same injector is immediately matched to this explicit binding, which means extensions
 * cannot override this binding. This is because the lookup is always short-circuited in this
 * specific situation (plain @Inject request, and plain explicit binding for the same type.)
 *
 * The simplest solution is to use a custom @Named here so it isn't bound under the plain key.
 * This is only necessary for default components using @Typed that want to support overriding.

0000\cocoartf824\cocoasubrtf410 {\fonttbl\f0\fswiss\fcharset77 Helvetica-Oblique;} {\colortbl;\red255\green255\blue255;} \pard\tx560\tx1120\tx1680\tx2240\tx2800\tx3360\tx3920\tx4480\tx5040\tx5600\tx6160\tx6720\qc\pardirnatural \f0\i\fs24 \cf0 if binding spec \ uses plugin prefix}ClassLineGraphicHead{623.954, 304}{652.046, 222}StylestrokeHeadArrow{488, 317}{555, 317}StylestrokeHeadArrow{453.532, 330}{575.468, 366}StylestrokeHeadArrow{83.5916, 196}{84, 138}{256, 138}{466, 138}{656, 138}{671.008, 9...

import java.util.List;

import org.apache.maven.execution.MavenExecutionRequest;
import org.apache.maven.project.MavenProject;
import org.apache.maven.project.ProjectBuildingException;

/**
 * Describes strategies for finding projects that Maven could build.
 */
public interface ProjectCollectionStrategy {
    /**
     *
     * @param request
     * @return
     * @throws ProjectBuildingException
     */