<groupId>org.apache.maven.its.mng0522</groupId>
    <artifactId>parent</artifactId>
    <version>1.0-SNAPSHOT</version>
  </parent>

  <artifactId>child-project</artifactId>
  <version>1.0-SNAPSHOT</version>
  <!-- NOTE: The upper-case packaging name is intentional and triggers a special mode in the EmptyLifecycleExecutor -->
  <packaging>JAR</packaging>

  <build>
    <plugins>
      <plugin>

     * @return the assembled toolchains, never {@code null}
     */
    @Nonnull
    PersistedToolchains getEffectiveToolchains();

    /**
     * Gets the problems that were encountered during the settings building. Note that only problems of severity
     * {@link BuilderProblem.Severity#WARNING} and below are reported here. Problems with a higher severity level cause
     * the settings builder to fail with a {@link ToolchainsBuilderException}.

import org.eclipse.aether.artifact.Artifact;
import org.eclipse.aether.resolution.ArtifactDescriptorException;
import org.eclipse.aether.resolution.ArtifactDescriptorResult;

/**
 * Maven relocation source.
 * Note: implementations of this component should avoid the "default" name (has special meaning in Eclipse Sisu) and
 * explicitly order implementations using Sisu priorities.
 *
 * @since 4.0.0
 */

    plugin version than the parent.
  </description>

  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.its.plugins</groupId>
        <artifactId>maven-it-plugin-a</artifactId>
        <!-- NOTE: Use different version than parent -->
        <version>2.0</version>
        <executions>
          <execution>
            <id>child-1</id>
            <phase>child-1</phase>
          </execution>

/**
 */
public class LifeCyclePluginAnalyzerStub implements LifeCyclePluginAnalyzer {
    public Set<Plugin> getPluginsBoundByDefaultToAllLifecycles(String packaging) {
        Set<Plugin> plugins;

        // NOTE: The upper-case packaging name is intentional, that's a special hinting mode used for certain tests
        if ("JAR".equals(packaging)) {
            plugins = new LinkedHashSet<>();

      <plugin>
        <groupId>org.apache.maven.its.plugins</groupId>
        <artifactId>maven-it-plugin-a</artifactId>
        <version>2.1-SNAPSHOT</version>
        <executions>
          <execution>
            <!-- NOTE: Explicitly reference "default" id here -->
            <id>default</id>
            <phase>child-default</phase>
          </execution>
          <execution>
            <id>non-default</id>

  <packaging>pom</packaging>

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

              <phase>validate</phase>
              <goals>
                <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>

  <packaging>jar</packaging>

  <name>Maven Integration Test :: it0052</name>
  <description>Test that source attachment doesn't take place when -DperformRelease=true is missing.</description>

  <!-- NOTE: Use stub versions of the core plugins referenced by the build -->
  <build>
    <pluginManagement>
      <plugins>
        <plugin>
          <artifactId>maven-compiler-plugin</artifactId>

    A depends on property B, and property B depends on property C and so on.
  </description>

  <properties>
    <!--
    NOTE: Both the ordering (i.e. neither ascending nor descending) and the number of properties is crucial to
    exhibit the bug.
    -->
    <property23>${property22}</property23>
    <property21>${property20}</property21>