-->

<!--
NOTE: This POM's XML declaration intentionally declares Latin-1 encoding.
-->

<project>
  <modelVersion>4.0.0</modelVersion>

  <groupId>org.apache.maven.its.mng2254</groupId>
  <artifactId>latin-1</artifactId>
  <version>0.1-SNAPSHOT</version>
  <packaging>pom</packaging>

  <name>Maven Integration Test :: MNG-2254 :: Latin-1</name>
  <description>TEST-CHARS: �������</description>

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

 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>

String, Iterable<? extends SelfDescribing>) - Method in class org.hamcrest.Description.NullDescription appendText(String) - Method in class org.hamcrest.BaseDescription appendText(String) - Method in interface org.hamcrest.Description Appends some plain text to the description. appendText(String) - Method in class org.hamcrest.Description.NullDescription appendValue(Object) - Method in class org.hamcrest.BaseDescription appendValue(Object) - Method in interface org.hamcrest.Description Appends an...

     2. append happens at plugin level first, then goal level, independently from phases.
        This means for example that adding pluginA:goal2 to pre-existing (pluginA:goal1, pluginB:goal) will lead to (pluginA:goal1, pluginA:goal2, pluginB:goal)

   * see effective POM as shown by {{{/plugins/maven-help-plugin/effective-pom-mojo.html}<<<help:effective-pom>>>}} to see the effective plugins then goals order.

        <plugins>
            <!--
            Both "org.apache" and "org.codehaus" are default providers of MOJO plugins
            which are especially dedicated to Maven projects.
            The MOJO stands for "Maven plain Old Java Object".
            Each mojo is an executable goal in Maven, and a plugin is a distribution of
            one or more related mojos.

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