</field>
        <field>
          <name>packaging</name>
          <version>4.0.0+</version>
          <description>
            The type of artifact this project produces, for example {@code jar},
              {@code war},
              {@code ear},
              {@code pom}.
            Plugins can create their own packaging, and
            therefore their own packaging types,

  <modelVersion>4.0.0</modelVersion>
  <groupId>com.google.guava</groupId>
  <artifactId>guava-parent</artifactId>
  <version>999.0.0-HEAD-android-SNAPSHOT</version>
  <packaging>pom</packaging>
  <name>Guava Maven Parent</name>
  <description>Parent for guava artifacts</description>
  <url>https://github.com/google/guava</url>
  <inceptionYear>2010</inceptionYear>
  <licenses>
    <license>

  <modelVersion>4.0.0</modelVersion>
  <groupId>com.google.guava</groupId>
  <artifactId>guava-parent</artifactId>
  <version>999.0.0-HEAD-jre-SNAPSHOT</version>
  <packaging>pom</packaging>
  <name>Guava Maven Parent</name>
  <description>Parent for guava artifacts</description>
  <url>https://github.com/google/guava</url>
  <inceptionYear>2010</inceptionYear>
  <licenses>
    <license>

 * the {@code /project/subprojects/subproject} elements of the POM in the aggregator project.
 * Note that the aggregator project is required to have a {@code pom} packaging.</p>
 *
 * <p><dfn>Project inheritance</dfn> defines a parent-child relationship between projects.
 * The <dfn>child project</dfn> inherits all the information from the <dfn>parent project</dfn>
 * POM.</p>
 *
 */

                        .setMessage("Invalid packaging for parent POM " + ModelProblemUtils.toSourceHint(parentModel)
                                + ", must be \"pom\" but is \"" + parentModel.getPackaging() + "\"")
                        .setLocation(parentModel.getLocation("packaging")));
            }
        } else {
            parentData = null;
        }

    @Test
    void testParentPomPackagingMustBePom() throws Exception {
        assertThrows(
                ProjectBuildingException.class,
                () -> buildPom("parent-pom-packaging/sub"),
                "Wrong packaging of parent POM was not rejected");
    }

    /** MNG-522, MNG-3018 */
    @Test
    void testManagedPluginConfigurationAppliesToImplicitPluginsIntroducedByPackaging() throws Exception {

            <type>ActivationFile</type>
          </association>
        </field>
        <field>
          <name>packaging</name>
          <version>1.2.0+</version>
          <type>String</type>
          <description>
            Specifies that this profile will be activated based on the project's packaging.
          </description>
        </field>
        <field>
          <name>condition</name>

     * <ul>
     *   <li>The project's artifacts ({@link Project#getArtifacts()}):
     *     <ul>
     *       <li>The POM artifact (always present)</li>
     *       <li>The main project artifact (if applicable based on packaging)</li>
     *     </ul>
     *   </li>
     *   <li>All attached artifacts in the order they were attached</li>
     * </ul>
     * The contents depend on the current lifecycle phase when this method is called, as artifacts

        & $installDir\python.exe -m pip install --upgrade pip; \
        \
        Write-Host 'Installing/updating packages...'; \
        & $installDir\python.exe -m pip install --upgrade setuptools packaging; \
        \
        Write-Host 'Removing installation binary...'; \
        Remove-Item C:\tmp\pyinstall.exe -Force; \
    }; \
    Write-Host 'Installing multiple Python versions...'; \
    $versions = @( \

                    current = topDirectory.relativize(current);
                }
                logger.info("  from " + current);
            }

            // ----------[ packaging ]----------
            prefix = chars('-', Math.max(0, (lineLength - project.getPackaging().length() - 4) / 2));
            suffix = chars('-', Math.max(0, lineLength - project.getPackaging().length() - 4 - prefix.length()));