<modelVersion>4.0.0</modelVersion>
  <groupId>example.eclipse-548652</groupId>
  <artifactId>parent</artifactId>
  <version>0.0.1-SNAPSHOT</version>
  <packaging>pom</packaging>
  <modules>
    <module>child</module>
  </modules>

<project>
  <modelVersion>4.0.0</modelVersion>

  <parent>
    <groupId>lifecycle-participant-reactor-dependency-injection</groupId>
    <artifactId>parent</artifactId>
    <version>1.0</version>
  </parent>

  <artifactId>module-a</artifactId>

under the License.
-->

<project>
  <modelVersion>4.0.0</modelVersion>
  <artifactId>foo</artifactId>
  <groupId>foo</groupId>
  <version>99.44</version>
  <packaging>bleh</packaging>
  <dependencyManagement>
    <dependencies>
      <dependency>
        <artifactId>artifactId</artifactId>
        <groupId>groupId</groupId>
      </dependency>
    </dependencies>
  </dependencyManagement>

import org.apache.maven.api.model.Prerequisites;
import org.apache.maven.api.model.Profile;
import org.apache.maven.api.services.Lookup;
import org.apache.maven.api.services.LookupException;
import org.apache.maven.artifact.ArtifactUtils;
import org.apache.maven.execution.BuildResumptionAnalyzer;
import org.apache.maven.execution.BuildResumptionDataRepository;
import org.apache.maven.execution.BuildResumptionPersistenceException;

        return dependency;
    }

    private MavenProject createSkippedMavenProject(String artifactId) {
        return createMavenProject(artifactId);
    }

    private MavenProject createSucceededMavenProject(String artifactId) {
        MavenProject project = createMavenProject(artifactId);
        executionResult.addBuildSummary(new BuildSuccess(project, 0));
        return project;
    }

  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">
  <modelVersion>4.0.0</modelVersion>

  <groupId>inheritance</groupId>
  <artifactId>parent</artifactId>
  <version>11-SNAPSHOT</version>

  <name>Model inheritance test</name>
  <description>Model inheritance description</description>
  <url>http://www.apache.org/</url>

  <mailingLists>

<project>
  <modelVersion>4.0.0</modelVersion>
  <groupId>maven-test</groupId>
  <artifactId>t07-c</artifactId>
  <packaging>jar</packaging>
  <version>1.0</version>
  <dependencies>
    <dependency>
      <groupId>maven-test</groupId>
      <artifactId>t07-d</artifactId>
      <version>1.1</version>
      <type>jar</type>
      <scope>compile</scope>
      <optional>true</optional>
    </dependency>
  </dependencies>

  particularly when we move mojos to a singleton instantiation model, and then
  run a reactorized project...the successive calls may leave behind configuration
  artifacts from invocation to invocation.

Maven Modifications

* DefaultPluginManager

  s/getMojoConfiguration()/getConfiguration()/g

  That should re-enable usage of mojo configuration. Ideally, we won't need any

  <groupId>maven-test</groupId>
  <artifactId>t08-a</artifactId>
  <packaging>jar</packaging>
  <version>1.0</version>
  <repositories>
    <repository>
      <id>central</id>
      <name>Fake Maven Central Repository</name>
      <url>file://dummy</url>
    </repository>
  </repositories>
  <dependencies>
    <dependency>
      <groupId>maven-test</groupId>
      <artifactId>t08-b</artifactId>
      <version>1.0</version>

<project>
  <modelVersion>4.0.0</modelVersion>
  <groupId>maven</groupId>
  <artifactId>p0</artifactId>
  <packaging>pom</packaging>
  <version>1.0</version>

  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-compiler-plugin</artifactId>
        <executions>
          <execution>
            <id>test</id>

            <!--  The key to this test... -->