<goal>parent-2</goal>
              </goals>
            </execution>
            <execution>
              <!-- NOTE: <id> deliberately omitted to use default value -->
              <phase>validate</phase>
              <goals>
                <goal>parent-default</goal>
              </goals>
            </execution>
          </executions>
        </plugin>
      </plugins>
    </pluginManagement>
  </build>

import org.apache.maven.api.services.LifecycleRegistry;
import org.apache.maven.api.services.PackagingRegistry;
import org.apache.maven.internal.impl.model.DefaultLifecycleBindingsInjector;

import static org.apache.maven.api.Lifecycle.DEFAULT;

@Singleton
@Named
@Priority(5)
public class EmptyLifecycleBindingsInjector extends DefaultLifecycleBindingsInjector {

    private static LifecycleRegistry lifecycleRegistry;

                problems.messages.get(0), "'profiles.profile[default].repositories.repository.id' must not be 'local'");
        assertContains(
                problems.messages.get(1),
                "'profiles.profile[default].repositories.repository.url' for local is missing");
        assertContains(
                problems.messages.get(2),

    }

    public ArtifactRepository createDefaultRemoteRepository() throws InvalidRepositoryException {
        return createRepository(
                RepositorySystem.DEFAULT_REMOTE_REPO_URL,
                RepositorySystem.DEFAULT_REMOTE_REPO_ID,
                true,
                ArtifactRepositoryPolicy.UPDATE_POLICY_DAILY,
                false,
                ArtifactRepositoryPolicy.UPDATE_POLICY_DAILY,

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
     *

    /**
     * name of the bean property used to get/set the field: by default, field name is used.
     * @return the name of the bean property
     */
    @Nonnull
    String name() default "";

    /**
     * alias supported to get parameter value.
     * @return the alias
     */
    @Nonnull
    String alias() default "";

    /**

/**
 * This realizes the metadata source via the default hint to provide backward-compat with Maven 2.x whose Plexus version
 * registered component descriptors twice: once keyed by role+roleHint and once keyed by role only. This effectively
 * made the metadata source available with its original role hint ("maven") as well as the default hint.
 *
 */
@Named
@Singleton
@Deprecated

 * Currently, this modification would create compatibility problems for existing plugins.
 */
public class DuplicateArtifactAttachmentException extends RuntimeException {

    private static final String DEFAULT_MESSAGE = "Duplicate artifact attachment detected.";

    private Artifact artifact;

    private final MavenProject project;

    public DuplicateArtifactAttachmentException(MavenProject project, Artifact artifact) {

        org.apache.maven.api.RemoteRepository remoteRepository = session.getRemoteRepository(
                new RemoteRepository.Builder("mirror", "default", "file:target/test-classes/repo").build());
        this.session = session.withLocalRepository(localRepository)
                .withRemoteRepositories(Collections.singletonList(remoteRepository));

  <packaging>JAR</packaging>

  <name>Maven Integration Test :: MNG-4341</name>
  <description>
    Test that plugins bound to the same phase get executed in POM order even if one of the plugins participates
    in the default lifecycle bindings for the project's packaging.
  </description>

  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.its.plugins</groupId>