import java.util.List;

import org.apache.maven.execution.MavenSession;
import org.apache.maven.lifecycle.LifecycleExecutionException;

/**
 * Interface allows overriding default mojo execution strategy For example it is possible wrap some mojo execution to
 * decorate default functionality or skip some executions
 */
public interface MojosExecutionStrategy {

    /**
     * Entry point to the execution strategy
     *

import javax.inject.Singleton;

import java.util.List;

import org.apache.maven.execution.MavenSession;
import org.apache.maven.lifecycle.LifecycleExecutionException;

/**
 * Default mojo execution strategy. It just iterates over mojo executions and runs one by one
 */
@Named
@Singleton
public class DefaultMojosExecutionStrategy implements MojosExecutionStrategy {
    @Override

/**
 * Extension point that allows build extensions observe and possibly veto mojo executions.
 * <p>
 * Unlike {@link org.apache.maven.execution.MojoExecutionListener}, this extension point does not
 * trigger instantiation of the component, hence "weak" class name prefix. Only applies to mojo execution
 * scoped components.
 * </p>

     *
     * @return the current project or {@code empty()} if not applicable
     */
    @Nonnull
    Optional<Project> getProject();

    /**
     * Gets the current mojo execution (if any).
     *
     * @return the current mojo execution or {@code empty()} if not applicable
     */
    @Nonnull
    Optional<MojoExecution> getMojoExecution();

    /**
     * Gets the exception that caused the event (if any).

        return style(".strong:-bold", message);
    }

    /**
     * Append message content in mojo style.
     * By default, green
     *
     * @param message the message to append
     * @return the current builder
     */
    @Nonnull
    default MessageBuilder mojo(Object message) {
        return style(".mojo:-f:green", message);
    }

    /**
     * Append message content in project style.

/**
 * Lifecycle mapping delegate component interface. Calculates project build execution plan given {@link Lifecycle} and
 * lifecycle phase. Standard lifecycles use plugin execution {@code <phase>} or mojo default lifecycle phase to
 * calculate the execution plan, but custom lifecycles can use alternative mapping strategies.
 */
@Named(DefaultLifecycleMappingDelegate.HINT)
@Singleton

import java.util.Collections;
import java.util.LinkedHashMap;
import java.util.List;
import java.util.Map;
import java.util.Optional;
import java.util.function.Function;
import java.util.stream.Collectors;

/**
 * Mojo (goals) bindings to a lifecycle phase.
 *
 * @see LifecycleMojo
 */
public class LifecyclePhase {

    private List<LifecycleMojo> mojos;

    public LifecyclePhase() {}

import java.lang.reflect.Array;

import org.codehaus.plexus.component.configurator.ConfigurationListener;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;

/**
 * Log at debug level the mojo configuration.
 *
 */
@Deprecated
public class DebugConfigurationListener implements ConfigurationListener {
    private final Logger logger;

    /**

import org.apache.maven.plugin.descriptor.Parameter;
import org.codehaus.plexus.component.configurator.expression.ExpressionEvaluator;
import org.codehaus.plexus.configuration.PlexusConfiguration;

/**
 * Print warnings if deprecated mojo or parameters of plugin are used in configuration.
 *
 */
@Singleton
@Named
class DeprecatedPluginValidator extends AbstractMavenPluginDescriptorSourcedParametersValidator {

xus/plexus-container-default/pom.xml 4.0.0 org.codehaus.plexus plexus-containers 1.0-alpha-32 plexus-container-default Default Plexus Container 1.0-alpha-32 maven-surefire-plugin once **/Test*.java **/Abstract*.java shade-maven-plugin org.codehaus.mojo 1.0-alpha-9 package shade classworlds:classworlds junit:junit jmock:jmock org.codehaus.plexus:plexus-classworlds org.codehaus.plexus:plexus-utils org.codehaus.plexus plexus-component-api org.codehaus.plexus plexus-utils org.codehaus.plexus plexus-classworlds...