@Singleton
public final class CleanLifecycleProvider extends AbstractLifecycleProvider {
    static final String LIFECYCLE_ID = "clean";

    // START SNIPPET: clean
    private static final String[] PHASES = {"pre-clean", "clean", "post-clean"};

    private static final String MAVEN_CLEAN_PLUGIN_VERSION = "3.2.0";

    private static final String[] BINDINGS = {

@Singleton
public final class DefaultLifecycleProvider extends AbstractLifecycleProvider {
    static final String LIFECYCLE_ID = "default";

    // START SNIPPET: default
    private static final String[] PHASES = {
        "validate",
        "initialize",
        "generate-sources",
        "process-sources",
        "generate-resources",
        "process-resources",
        "compile",
        "process-classes",

@Singleton
public final class SiteLifecycleProvider extends AbstractLifecycleProvider {
    static final String LIFECYCLE_ID = "site";

    // START SNIPPET: site
    private static final String[] PHASES = {"pre-site", "site", "post-site", "site-deploy"};

    private static final String MAVEN_SITE_PLUGIN_VERSION = "3.12.1";

    private static final String[] BINDINGS = {

/**
 * Base lifecycle provider.
 */
public abstract class AbstractLifecycleProvider implements Provider<Lifecycle> {
    private final Lifecycle lifecycle;

    protected AbstractLifecycleProvider(String id, String[] phases, String[] pluginBindings) {
        HashMap<String, LifecyclePhase> defaultBindings = null;
        if (pluginBindings != null) {
            final int len = pluginBindings.length;

            if (len < 2 || len % 2 != 0) {

We have a lifecycle mapping for the packaging of *jar* below. You see that for this packaging we have a *default* lifecycle and a list of phases where each phase is a comma separated list of goals to run and they are in the form groupId:artifactId:version.

<configuration>
  <lifecycles>
    <lifecycle>
      <id>default</id>
      <phases>
        <process-resources>org.apache.maven.plugins:maven-resources-plugin:resources</process-resources>

                        + " You must specify a valid lifecycle phase or a goal in the format <plugin-prefix>:<goal> or"
                        + " <plugin-group-id>:<plugin-artifact-id>[:<plugin-version>]:<goal>."
                        + " Available lifecycle phases are: " + defaultLifeCycles.getLifecyclePhaseList() + ".");
            }

            if (logger.isDebugEnabled()) {

 */
package org.apache.maven.api;

import java.util.Optional;

import org.apache.maven.api.annotations.Experimental;
import org.apache.maven.api.annotations.Nonnull;

/**
 * Event sent by maven during various phases of the build process.
 * Such events can be listened to using {@link Listener}s objects
 * registered in the {@link Session}.
 *
 * @since 4.0.0
 */
@Experimental
public interface Event {

    /**

    }

    /**
     * Get lifecycle based on phase
     *
     * @param phase
     * @return
     */
    public Lifecycle get(String phase) {
        return getPhaseToLifecycleMap().get(phase);
    }

    /**
     * We use this to map all phases to the lifecycle that contains it. This is used so that a user can specify the
     * phase they want to execute and we can easily determine what lifecycle we need to run.

        </field>
        <field>
          <name>phases</name>
          <version>1.0.0</version>
          <description>The phase mappings for this lifecycle.</description>
          <association>
            <type>Phase</type>
            <multiplicity>*</multiplicity>
          </association>
        </field>
      </fields>
    </class>
    <class>
      <name>Phase</name>
      <version>1.0.0</version>

                TEST.getPhase(),
                PROCESS_TEST_RESOURCES.getPhase(),
                PACKAGE.getPhase(),
                "BEER",
                INSTALL.getPhase());

        // The two phases below are really for future expansion, some would say they lack a drink
        // The point being that they do not really have to match the "real" stuff,