<build>
    <resources>
      <resource>
        <directory>${pom.build.directory}/generated-resources/plexus</directory>
      </resource>
    </resources>

    <filters>
      <filter>${pom.build.directory}/generated-filters.properties</filter>
    </filters>

    <directory>target</directory>

    <sourceDirectory>${pom.basedir}/src/main/java</sourceDirectory>

    Verify that filter definitions are properly merged.
  </description>

  <build>
    <filters>
      <filter>src/main/filters/child-a.properties</filter>
      <filter>src/main/filters/child-c.properties</filter>
      <filter>src/main/filters/child-b.properties</filter>
      <filter>src/main/filters/child-d.properties</filter>
    </filters>
  </build>

    /**
     * Interpolates expressions in the specified model. Note that implementations are free to either interpolate the
     * provided model directly or to create a clone of the model and interpolate the clone. Callers should always use
     * the returned model and must not rely on the input model being updated.
     *
     * @param model The model to interpolate, must not be {@code null}.

  <build>
    <resources>
      <resource>
        <directory>${pom.build.directory}/generated-resources/plexus</directory>
      </resource>
    </resources>

    <filters>
      <filter>${pom.build.directory}/generated-filters.properties</filter>
    </filters>

    <directory>target</directory>

    <sourceDirectory>src/main/java</sourceDirectory>
    <testSourceDirectory>src/test/java</testSourceDirectory>

                    .resources(map(build.getResources(), r -> alignToBaseDirectory(r, basedir)))
                    .testResources(map(build.getTestResources(), r -> alignToBaseDirectory(r, basedir)))
                    .filters(map(build.getFilters(), s -> alignToBaseDirectory(s, basedir)))
                    .outputDirectory(alignToBaseDirectory(build.getOutputDirectory(), basedir))

        </includes>
        <excludes>
          <exclude>test.excluded</exclude>
        </excludes>
      </testResource>
    </testResources>
    <filters>
      <filter>src/main/filter/it.properties</filter>
    </filters>

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

        }
    }

    /*
     * TODO: Whether duplicates should be removed looks like an option for the generated merger.
     */
    @Override
    protected void mergeBuildBase_Filters(
            BuildBase.Builder builder,
            BuildBase target,
            BuildBase source,
            boolean sourceDominant,
            Map<Object, Object> context) {

import org.apache.maven.api.services.DependencyResolverResult;

/**
 * The result of collecting dependencies with a dependency resolver.
 * New instances are initially empty. Callers must populate with calls
 * to the following methods, in that order:
 *
 * <ul>
 *   <li>{@link #addOutputDirectory(Path, Path, PathModularizationCache)} (optional)</li>

// The plugin manager should load up a directory structure of plugins.
// - a plugin per directory where the plugin is present with its deps
// - a plugin that has its dependencies packaged up with it
// - implement filters and create a test where a plugin fails if the right classes are not filtered
// - plugins with a dependency the same as the core but different versions, make it fail then fix it

  /*
 *
 * h2. Concerns for the plugin manager

s.class package org.junit.internal.runners.statements; public synchronized class RunAfters extends org.junit.runners.model.Statement { private final org.junit.runners.model.Statement next; private final Object target; private final java.util.List afters; public void RunAfters(org.junit.runners.model.Statement, java.util.List, Object); public void evaluate() throws Throwable; protected void invokeMethod(org.junit.runners.model.FrameworkMethod) throws Throwable; } org/junit/internal/runners/statem...