<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>
        <groupId>org.apache.maven.its.plugins</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.plugins</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.plugins</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>
          <groupId>org.apache.maven.its.plugins</groupId>

          </plugins>
      </build>
    </profile>
    <profile>
      <!--
          Passes JDK 11-12-specific `no-module-directories` flag to Javadoc tool,
          which is required to make symbol search work correctly in the generated
          pages.

          This flag does not exist on 9-10 and 13+ (https://bugs.openjdk.java.net/browse/JDK-8215582).

            lines could make c.g.c.base.testModule transitively inherit from extra modules. If some
            of those modules are ones that it uses but forgets to list in its own <inherits>, we'd
            like to get an error. Currently we do, but if we add the extra <inherits> lines, we
            won't.

            I have one idea for a better approach, but it's painful, and I haven't tested it: We

            {@code partner}
            (directly synced from a partner Maven 2 repository), {@code deployed} (was deployed from a Maven 2
            instance), {@code verified} (has been hand verified as correct and final).
          </description>
          <required>false</required>
          <type>String</type>
        </field>
      </fields>
    </class>
    <class>
      <name>License</name>