<version>0.1</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>

    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.gwt.core.Core" />
<inherits name="com.google.gwt.user.User" />

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

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

				<version>3.6.2</version>
				<configuration>
					<encoding>UTF-8</encoding>
					<docencoding>UTF-8</docencoding>
					<charset>UTF-8</charset>
					<source>8</source>
					<doclint>none</doclint>
				</configuration>
			</plugin>
			<plugin>
				<artifactId>maven-jar-plugin</artifactId>
				<version>3.3.0</version>
				<configuration>
					<archive>
						<manifestEntries>

  <groupId>org.apache.maven.its.mng</groupId>
  <artifactId>parent</artifactId>
  <version>0.1</version>
  <packaging>pom</packaging>

  <!--
  NOTE: This extends the test to check an edge case of URL adjustment which must not error out during inheritance
  if the child misses the artifactId (as to be reported by validation).
  -->
  <url>https://maven.apache.org/</url>

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>

    plugin version than the parent.
  </description>

  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.its.plugins</groupId>
        <artifactId>maven-it-plugin-a</artifactId>
        <!-- NOTE: Use different version than child -->
        <version>1.0</version>
        <executions>
          <execution>
            <id>parent-1</id>
            <phase>parent-1</phase>
          </execution>

    version.
  </description>

  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.its.plugins</groupId>
        <artifactId>maven-it-plugin-a</artifactId>
        <!-- NOTE: <version> element deliberately omitted here -->
        <executions>
          <execution>
            <id>child-1</id>
            <phase>child-1</phase>
          </execution>
          <execution>

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