<stringParam>CHILD-1</stringParam>
            <stringParam>CHILD-3</stringParam>
            <stringParam>CHILD-2</stringParam>
            <stringParam>CHILD-4</stringParam>
          </stringParams>
          <listParam combine.children="append">
            <!-- NOTE: These values are deliberately not in alpha order! -->
            <listParam>CHILD-1</listParam>

          <version>2.1-SNAPSHOT</version>
          <inherited>true</inherited>
          <configuration>
            <listParam>
              <!-- NOTE: These values are deliberately not in alpha order! -->
              <listParam>PARENT-1</listParam>
              <listParam>PARENT-3</listParam>
              <listParam>PARENT-2</listParam>
              <listParam>PARENT-4</listParam>
            </listParam>

  2005-04-29

Abstract

  We're moving toward integrating mojos as first-class plexus components, while
  at the same time avoiding introducing required plexus dependencies into the
  mojo development model.

  In order to really achieve this, we need mojo configurations (which are
  provided both in terms of static expressions that are just looked up, and
  in terms of user-provided configuration from properties or the POM).

        // file. Ideally, we'd do full pattern-evaluation against the sysprops, but this
        // is a first step. There are several replacements below, in order to normalize
        // the path character before we operate on the string as a regex input, and
        // in order to avoid surprises with the File construction...
        // -------------------------------------------------------------------------------------

  <version>0.1</version>
  <packaging>pom</packaging>

  <name>Maven Integration Test :: MNG-3887</name>
  <description>
    Test that multiple plugin executions bound to the same phase are executed in the order given by the POM.
  </description>

  <build>
    <!-- This project uses plugin management for the test plugin -->
    <pluginManagement>
      <plugins>
        <plugin>

  <artifactId>test</artifactId>
  <version>1.0-SNAPSHOT</version>

  <name>Maven Integration Test :: MNG-4003</name>
  <description>
    Verify that dependencies survive the project construction in the POM order.
  </description>

  <dependencies>
    <dependency>
      <groupId>org.apache.maven.its.mng4003</groupId>
      <artifactId>a</artifactId>
      <version>1</version>
    </dependency>
    <dependency>

  <artifactId>test</artifactId>
  <version>1.0-SNAPSHOT</version>

  <name>Maven Integration Test :: MNG-4003</name>
  <description>
    Verify that dependencies survive the project construction in the POM order.
  </description>

  <dependencies>
    <dependency>
      <groupId>org.apache.maven.its.mng4003</groupId>
      <artifactId>a</artifactId>
      <version>1</version>
    </dependency>
    <dependency>

 maven.multiproject.includes property.
 2. it works without problems only for projects with relative paths, e.g., from
 one CVS repository.. for projects from multiple SCM repositories it's harder
 to maintain the same relative links on all developer computers.
 not sure the unified source directory structure addresses this issue.

 Properties

 maven.user.config.dir (system,default=${user.home}/.m2)

     * @return if the collection contains only one item returns the single item, otherwise creates a new
     *         {@link MavenChainedWorkspaceReader} chaining all readers in the order of the given collection.
     */
    public static WorkspaceReader of(Collection<WorkspaceReader> workspaceReaderCollection) {
        WorkspaceReader[] readers = workspaceReaderCollection.toArray(new WorkspaceReader[0]);

/**
 * Evaluator for plugin parameters expressions. Content surrounded by <code>${</code> and <code>}</code> is evaluated.
 * Recognized values are:
 * <table border="1">
 * <caption>Expression matrix</caption>
 * <tr><th>expression</th>                     <th></th>               <th>evaluation result</th></tr>
 * <tr><td><code>session.*</code></td>         <td></td>               <td></td></tr>