<description>
    Test that during inheritance/merging of a plugin execution the goals specified by child and parent are properly
    ordered.
  </description>

  <build>
    <!-- This project does not use plugin management for the test plugin -->
    <plugins>
      <plugin>
        <groupId>org.apache.maven.its.plugins</groupId>
        <artifactId>maven-it-plugin-a</artifactId>
        <version>1.0-SNAPSHOT</version>

  <description>
    Test that multiple plugin executions bound to the same phase are executed in the order given by the POM.
  </description>

  <build>
    <!-- This project does not use plugin management for the test plugin -->
    <plugins>
      <plugin>
        <groupId>org.apache.maven.its.plugins</groupId>
        <artifactId>maven-it-plugin-a</artifactId>
        <version>1.0-SNAPSHOT</version>

		<postConstruct name="addConfigFile">
			<arg>"fess"</arg>
			<arg>"tr/stemmer_override.txt"</arg>
		</postConstruct>
		<!-- fess index -->
		<postConstruct name="addIndexConfig">
			<arg>"fess/doc"</arg>
		</postConstruct>
		<!-- fess_config index -->
		<postConstruct name="addIndexConfig">
			<arg>"fess_config.access_token/access_token"</arg>
		</postConstruct>
		<postConstruct name="addIndexConfig">

specific language governing permissions and limitations
under the License.
-->

<project>
  <modelVersion>4.0.0</modelVersion>

  <!-- NOTE: The base directory name of this project deliberately does not match its artifact id! -->

  <parent>
    <groupId>org.apache.maven.its.mng3846</groupId>
    <artifactId>parent</artifactId>
    <version>0.1</version>
  </parent>

  <artifactId>ap</artifactId>

    Our workaround is to tell GWT that util.concurrent and all other packages
    have prod supersource, even if they have none. GWT is happy to ignore us
    when we specify a nonexistent path.

    (I hope that this workaround does not cause its own problems in the future.)
-->
<super-source path="super"/>

<inherits name="com.google.common.annotations.Annotations" />
<inherits name="com.google.gwt.core.Core" />

    Our workaround is to tell GWT that util.concurrent and all other packages
    have prod supersource, even if they have none. GWT is happy to ignore us
    when we specify a nonexistent path.

    (I hope that this workaround does not cause its own problems in the future.)
-->
<super-source path="super"/>

<inherits name="com.google.common.annotations.Annotations" />
<inherits name="com.google.gwt.core.Core" />

    Our workaround is to tell GWT that util.concurrent and all other packages
    have prod supersource, even if they have none. GWT is happy to ignore us
    when we specify a nonexistent path.

    (I hope that this workaround does not cause its own problems in the future.)
-->
<super-source path="super"/>

<inherits name="com.google.common.annotations.Annotations" />
<inherits name="com.google.common.escape.Escape" />

    Our workaround is to tell GWT that util.concurrent and all other packages
    have prod supersource, even if they have none. GWT is happy to ignore us
    when we specify a nonexistent path.

    (I hope that this workaround does not cause its own problems in the future.)
-->
<super-source path="super"/>

<inherits name="com.google.common.annotations.Annotations" />
<inherits name="com.google.common.escape.Escape" />

  <name>Maven Integration Test :: MNG-3906</name>
  <description>
    Test that project-level plugin dependencies are properly merged during inheritance.
  </description>

  <build>
    <!-- NOTE: This parent does not use plugin management -->
    <plugins>
      <plugin>
        <groupId>org.apache.maven.its.plugins</groupId>
        <artifactId>maven-it-plugin-class-loader</artifactId>
        <version>2.1-SNAPSHOT</version>

  <name>Maven Integration Test :: MNG-4000</name>
  <description>
    Test that plugin executions without id are not lost among other plugin executions.
  </description>

  <build>
    <!-- NOTE: This test does not use plugin management for the IT plugin. -->
    <plugins>
      <plugin>
        <groupId>org.apache.maven.its.plugins</groupId>
        <artifactId>maven-it-plugin-log-file</artifactId>