* Maven versions to support further events. Hence it is strongly recommended to derive custom listeners from
 * {@link AbstractExecutionListener} in order to avoid interoperability problems.
 *
 */
public interface ExecutionListener {

    void projectDiscoveryStarted(ExecutionEvent event);

    void sessionStarted(ExecutionEvent event);

  <name>Maven Integration Test :: MNG-4102</name>
  <description>
    Verify that the effective value of an inherited property reflects the values of any nested property
    as defined by the child. This boils down to the order of inheritance and (parent) interpolation.
  </description>

  <properties>
    <overridden>PARENT</overridden>
    <!-- Test the effective value of this property in the child when "overridden" is defined by child as well -->

  <name>Maven Integration Test :: MNG-4102 :: Child</name>
  <description>
    Verify that the effective value of an inherited property reflects the values of any nested property
    as defined by the child. This boils down to the order of inheritance and (parent) interpolation.
  </description>

  <properties>
    <overridden>CHILD</overridden>
  </properties>

 *
 * @since 4.0.0
 */
@Experimental
@Consumer
public interface VersionRangeResolver extends Service {

    /**
     * Expands a version range to a list of matching versions, in ascending order.
     * For example, resolves "[3.8,4.0)" to "3.8", "3.8.1", "3.8.2".
     * The returned list of versions is only dependent on the configured repositories and their contents.

  <modules>
    <module>simple-weather</module>
    <module>simple-webapp</module>

    <!-- On purpose at the end, project graph is responsible for ordering -->
    <!-- Build/consumer should not be effected by reverse order -->
    <module>simple-testutils</module>
    <module>utils-parent</module>
  </modules>

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

  <artifactId>test</artifactId>
  <version>0.1</version>
  <packaging>pom</packaging>

  <name>Maven Integration Test :: MNG-3808</name>
  <description>
    Test the reports are executed in the order given in the POM.
  </description>

  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.its.plugins</groupId>
        <artifactId>maven-it-plugin-log-file</artifactId>

    private String lifecyclePhase;

    /**
     * The executions to fork before this execution, indexed by the groupId:artifactId:version of the project on which
     * the forked execution are to be run and in reactor build order.
     */
    private Map<String, List<MojoExecution>> forkedExecutions = new LinkedHashMap<>();

    public MojoExecution(Plugin plugin, String goal, String executionId) {
        this.plugin = plugin;

        </field>
        <field>
          <name>activeProfiles</name>
          <version>1.0.0</version>
          <description><![CDATA[
            List of manually-activated build profiles, specified in the order in which
            they should be applied.
          ]]></description>
          <association>
            <type>String</type>
            <multiplicity>*</multiplicity>
          </association>
        </field>

fields in a Plexus component. Typically this is done within Plexus with the configuration supplied with component configuration, but in Maven we take configuration values from the POM. So we have to use the ComponentConfigurator outside of Plexus in order to configure the Maven Mojo which is just a Plexus component. We can use the information from the MojoDescriptor along with the merged configuration information that is now present in the POM to create the complete PlexusConfiguration used to populate...

        <field xdoc.separator="blank">
          <name>activeProfiles</name>
          <version>1.0.0+</version>
          <description>
            List of manually-activated build profiles, specified in the order in which
            they should be applied.
          </description>
          <association>
            <type>String</type>
            <multiplicity>*</multiplicity>
          </association>
        </field>