</field>
        <field>
          <name>checksumPolicy</name>
          <version>1.0.0+</version>
          <description>
            What to do when verification of an artifact checksum fails. Valid values are "fail" (default for Maven 4 and
            above), "warn" (default for Maven 2 and 3) or "ignore".
          </description>
          <type>String</type>
        </field>
      </fields>
    </class>

     * {@link BuilderProblem.Severity#WARNING} and below are reported here. Problems with a higher severity level cause
     * the settings builder to fail with a {@link SettingsBuilderException}.
     *
     * @return the problems that were encountered during the settings building, can be empty but never {@code null}
     */
    @Nonnull
    List<BuilderProblem> getProblems();

    private List<String> goals;

    private boolean useReactor = false;

    private boolean recursive = true;

    private File pom;

    private String reactorFailureBehavior = REACTOR_FAIL_FAST;

    private boolean resume = false;

    private String resumeFrom;

    private String makeBehavior;

    private Properties systemProperties;

    private Properties userProperties;

            ModelBuilderRequest request) {
        // We only check for groupId/artifactId/version/classifier cause if there is another
        // module with the same groupId/artifactId/version/classifier this will fail the build
        // earlier like "Project '...' is duplicated in the reactor.
        // So it is sufficient to check only groupId/artifactId/version/classifier and not the
        // packaging type.

public FailOnTimeout$Builder withLookingForStuckT(boolean); public FailOnTimeout build(org.junit.runners.model.Statement); } org/junit/internal/runners/statements/Fail.class package org.junit.internal.runners.statements; public synchronized class Fail extends org.junit.runners.model.Statement { private final Throwable error; public void Fail(Throwable); public void evaluate() throws Throwable; } org/junit/internal/runners/statements/RunBefores.class package org.junit.internal.runners.statements; public...

    /**
     * @param context the context, cannot be null
     * @param model   the model to transform
     * @param path    the pom file, cannot be null
     * @throws ModelTransformerException if the transformation fails
     */
    @Nonnull
    Model transform(@Nonnull ModelTransformerContext context, @Nonnull Model model, @Nonnull Path path)
            throws ModelTransformerException;

    /**
     * User property for chained LRM: list of "tail" local repository paths (separated by comma), to be used with
     * {@link ChainedLocalRepositoryManager}.
     * Default value: {@code null}, no chained LRM is used.
     *
     * @since 3.9.0
     */
    private static final String MAVEN_REPO_LOCAL_TAIL = "maven.repo.local.tail";

    /**

assumed to contain the desired class name. Look for a properties file named commons-logging.properties visible in the application class path, with a property named org.apache.commons.logging.LogFactory defining the desired implementation class name. Fall back to a default implementation, which is described further below. If a commons-logging.properties file is found, all of the properties defined there are also used to set configuration attributes on the instantiated LogFactory instance. Once an implementation...

        if (mojoExecutionConfigurator == null) {
            //
            // The plugin has a custom component configurator but does not have a custom mojo execution configurator
            // so fall back to the default mojo execution configurator.
            //
            mojoExecutionConfigurator = mojoExecutionConfigurators.get("default");
        }
        return mojoExecutionConfigurator;
    }

                                } catch (InterruptedException ie) {
                                    // ignore
                                }
                                file.delete(); // if this fails, forget about it
                            }
                        }
                    } catch (TransferFailedException e) {
                        getLogger()