plugins.add(newPlugin("maven-compiler-plugin", "compile", "testCompile"));
            plugins.add(newPlugin("maven-resources-plugin", "resources", "testResources"));
            plugins.add(newPlugin("maven-surefire-plugin", "test"));
            plugins.add(newPlugin("maven-jar-plugin", "jar"));
            plugins.add(newPlugin("maven-install-plugin", "install"));
            plugins.add(newPlugin("maven-deploy-plugin", "deploy"));
        } else {

  </build>
  <modules>
    <module>maven-archiver</module>
    <module>maven-artifact</module>
    <module>maven-artifact-manager</module>
    <module>maven-artifact-ant</module>
    <module>maven-artifact-test</module>
    <module>maven-core</module>
    <module>maven-error-diagnostics</module>
    <module>maven-model</module>
    <module>maven-monitor</module>
    <module>maven-plugin-api</module>

 * @param <V> the value type of the map to be tested.
 * @author George van den Driessche
 */
@GwtCompatible
@Ignore("test runners must not instantiate and run this directly, only via suites we build")
// @Ignore affects the Android test runner, which respects JUnit 4 annotations on JUnit 3 tests.
@SuppressWarnings("JUnit4ClassUsedInJUnit3")
@NullMarked

import java.util.logging.Logger;
import org.jspecify.annotations.NullMarked;

/**
 * Simple utility for when you want to create a {@link TearDown} that may throw an exception but
 * should not fail a test when it does. (The behavior of a {@code TearDown} that throws an exception
 * varies; see its documentation for details.) Use it just like a {@code TearDown}, except override
 * {@link #sloppyTearDown()} instead.
 *

  <parent>
    <groupId>inheritance</groupId>
    <artifactId>parent</artifactId>
    <version>11-SNAPSHOT</version>
  </parent>

  <artifactId>child-artifact-id</artifactId>
  <name>Model inheritance test parent: module directory != artifactId</name>
  <description>
    artifactId == "child-artifact-id"
    but expect path on SCM and site == "child"

    <groupId>inheritance</groupId>
    <artifactId>parent</artifactId>
    <version>11-SNAPSHOT</version>
  </parent>

  <artifactId>inheritance</artifactId><!-- same as directory name -->
  <name>Model urls inheritance test child</name>

  <scm>
    <url>https://domain.org/override</url><!-- check that this won't impact child.site.url.inherit.append.path attribute inheritance -->
  </scm>
  <distributionManagement>

    util.concurrent, like nearly all our packages, has two .gwt.xml files: one
    for prod and one for tests. However, unlike our other packages, as of this
    writing it has test supersource but no prod supersource.

    GWT happens to use the prod .gwt.xml, so it looks for no supersource for
    tests, either. This causes it to fail to find AtomicLongMapTest.

    // The local repository for this category of tests
    // ----------------------------------------------------------------------

    protected File getLocalRepositoryPath() {
        return getTestFile("target/test-classes/inheritance-repo/" + getTestSeries());
    }

    @Override
    @BeforeEach
    public void setUp() throws Exception {
        super.setUp();
        EmptyLifecycleBindingsInjector.useEmpty();
    }

    assertThat(manyValuesAccumulatorByAddAllStatsAccumulator.mean())
        .isWithin(ALLOWED_ERROR)
        .of(MANY_VALUES_MEAN);
    // For datasets of many double values created from an iterable, we test many combinations of
    // finite and non-finite values:
    for (ManyValues values : ALL_MANY_VALUES) {
      StatsAccumulator accumulator = new StatsAccumulator();

import org.apache.maven.project.ProjectBuildingException;
import org.apache.maven.project.ProjectBuildingResult;

/*

- test projects for each of these
- how to categorize the problems so that the id of the problem can be match to a page with descriptive help and the test
  project
- nice little sample projects that could be run in the core as well as integration tests

All Possible Errors