<groupId>org.apache.maven.its.mng3827</groupId>
  <artifactId>test2</artifactId>
  <version>1.0-SNAPSHOT</version>

  <name>Maven Integration Test :: MNG-3864</name>
  <description>
    Verify that plain per-execution plugin configuration works correctly.
  </description>

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

 * cannot override this binding. This is because the lookup is always short-circuited in this
 * specific situation (plain @Inject request, and plain explicit binding for the same type.)
 *
 * The simplest solution is to use a custom @Named here so it isn't bound under the plain key.
 * This is only necessary for default components using @Typed that want to support overriding.
 *

            }
        }

        if (!hasBeenPackagedDuringThisSession(project)) {
            // fallback to loose class files only if artifacts haven't been packaged yet
            // and only for plain old jars. Not war files, not ear files, not anything else.
            return determineBuildOutputDirectoryForArtifact(project, artifact);
        }

        // The fall-through indicates that the artifact cannot be found;

 Jason van Zyl
 Vincent Siveton
 Hervé Boutemy
 -----
 2011-06-12
 -----

Maven 4 API - Immutable Maven Model

 This is strictly the immutable model for Maven POM (Project Object Model), so really just plain objects in <<<org.apache.maven.api.model>>> package.

 The following are generated from this model:

   * {{{./apidocs/index.html}Java sources}} with <<<Builder>>> inner classes for immutable instances creation.

  <groupId>org.apache.maven.its.mng3827</groupId>
  <artifactId>test1</artifactId>
  <version>1.0-SNAPSHOT</version>

  <name>Maven Integration Test :: MNG-3827</name>
  <description>
    Verify that plain plugin configuration works correctly.
  </description>

  <build>
    <!-- This project does not use plugin management for the test plugin -->
    <plugins>
      <plugin>

  <groupId>org.apache.maven.its.mng3827</groupId>
  <artifactId>test2</artifactId>
  <version>1.0-SNAPSHOT</version>

  <name>Maven Integration Test :: MNG-3827</name>
  <description>
    Verify that plain plugin configuration works correctly.
  </description>

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

  <groupId>org.apache.maven.its.mng3827</groupId>
  <artifactId>test1</artifactId>
  <version>1.0-SNAPSHOT</version>

  <name>Maven Integration Test :: MNG-3864</name>
  <description>
    Verify that plain per-execution plugin configuration works correctly.
  </description>

  <build>
    <!-- This project does not use plugin management for the test plugin -->
    <plugins>
      <plugin>

            describe the project, such as on the website. While this element can be specified as
            CDATA to enable the use of HTML tags within the description, it is discouraged to allow
            plain text representation. If you need to modify the index page of the generated website,
            you are able to specify your own instead of adjusting this text.</description>
          <type>String</type>
        </field>

 */
public class MavenExecutionPlan implements Iterable<ExecutionPlanItem> {

    /*
      At the moment, this class is totally immutable, and this is in line with thoughts about the
      pre-calculated execution plan that stays the same during the execution.

      If deciding to add mutable state to this class, it should be at least considered to
      separate this into a separate mutable structure.

    */

+ Submit a pull request to the repository in the Apache organization.
+ Update your JIRA ticket and include a link to the pull request in the ticket.

If you plan to contribute on a regular basis, please consider filing a [contributor license agreement][cla].

Making Trivial Changes
----------------------

For changes of a trivial nature to comments and documentation, it is not always