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

    }

    @Override
    public Artifact createArtifact(String groupId, String artifactId, String version, String packaging) {
        return artifactFactory.createBuildArtifact(groupId, artifactId, version, packaging);
    }

    @Override
    public Artifact createArtifactWithClassifier(
            String groupId, String artifactId, String version, String type, String classifier) {

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

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

                    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()));

                    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()));

  By default, every model field is inherited as-is from parent, with a few exceptions that are intentionally not inherited:
  <<<modelVersion>>>, <<<artifactId>>>, <<<packaging>>>, <<<profiles>>> (injected in phase 1) and <<<prerequisites>>>.

  Notice that the 5 URLs from the model (<<<project.url>>>, <<<project.scm.connection>>>, <<<project.scm.developerConnection>>>,

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

                + artifact.getArtifactId() + "</artifactId>" + "<version>"
                + artifact.getBaseVersion() + "</version>" + "<packaging>"
                + artifact.getType() + "</packaging>" + "</project>";
        return new StubModelSource(xml, artifact);
    }

    /**

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