<artifactId>parent</artifactId>
  <version>1.0</version>
  <packaging>pom</packaging>

  <name>Maven Integration Test :: MNG-4008</name>
  <description>
    Verify that filter definitions are properly merged.
  </description>

  <build>
    <filters>
      <!-- NOTE: The first filter is deliberately defined by the child as well, so should not be added twice -->
      <filter>src/main/filters/child-a.properties</filter>

    <version>0.1</version>
  </parent>

  <artifactId>child</artifactId>

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

  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.its.plugins</groupId>
        <artifactId>maven-it-plugin-class-loader</artifactId>

            }
            return result;
        }

        public void merge(org.apache.maven.repository.legacy.metadata.ArtifactMetadata metadata) {
            // not used
        }

        public void merge(ArtifactMetadata metadata) {
            // not used
        }

    pragmatic software license, and a desire to create high quality software that leads the way in its field.
    We consider ourselves not simply a group of projects sharing a server, but rather a community of developers
    and users.
  </description>
  <licenses>
    <license>
      <name>The Apache Software License, Version 2.0</name>
      <url>http://www.apache.org/licenses/LICENSE-2.0.txt</url>

    pragmatic software license, and a desire to create high quality software that leads the way in its field.
    We consider ourselves not simply a group of projects sharing a server, but rather a community of developers
    and users.
  </description>
  <licenses>
    <license>
      <name>The Apache Software License, Version 2.0</name>
      <url>http://www.apache.org/licenses/LICENSE-2.0.txt</url>

  <version>0.1</version>
  <packaging>pom</packaging>

  <name>Maven Integration Test :: MNG-3925</name>
  <description>
    Test that plugin executions (in the same phase) are properly ordered after inheritance/merge with
    parent executions.
  </description>

  <build>
    <!-- This project uses plugin management for the test plugin -->
    <pluginManagement>
      <plugins>
        <plugin>

                        .artifactId(pluginInfo.artifactId)
                        .name(pluginInfo.name)
                        .build()))
                .build();
    }

    @Override
    protected void merge(Metadata recessive) {
        List<Plugin> recessivePlugins = recessive.getPlugins();
        List<Plugin> plugins = metadata.getPlugins();
        if (!recessivePlugins.isEmpty() || !plugins.isEmpty()) {

            versioning.latest(artifact.getBaseVersion());
        }

        metadata.versioning(versioning.build());

        return metadata.build();
    }

    @Override
    protected void merge(Metadata recessive) {
        Versioning original = metadata.getVersioning();

        Versioning.Builder versioning = Versioning.newBuilder(original);
        versioning.lastUpdated(fmt.format(timestamp));

        buffer.append(checksumPolicy);
        buffer.append(", updates=");
        buffer.append(updatePolicy);
        buffer.append('}');
        return buffer.toString();
    }

    public void merge(ArtifactRepositoryPolicy policy) {
        if (policy != null && policy.isEnabled()) {
            setEnabled(true);

        Source userSource = request.getUserToolchainsSource().orElse(null);
        PersistedToolchains user = readToolchains(userSource, request, problems);

        PersistedToolchains effective = toolchainsMerger.merge(user, global, false, null);

        if (hasErrors(problems)) {
            throw new ToolchainsBuilderException("Error building toolchains", problems);
        }