# Testing Dependencies with Overrides

## Overriding dependencies during testing

There are some scenarios where you might want to override a dependency during testing.

You don't want the original dependency to run (nor any of the sub-dependencies it might have).

     * {@link ParserRequest#mvn(String[], Logger, MessageBuilderFactory)}.
     *
     * @param args the command-line arguments
     * @param logger the logger to use during parsing
     * @param messageBuilderFactory the factory for creating message builders
     * @return the parsed InvokerRequest
     * @throws ParserException if there's an error during parsing of the command or arguments

    Model getEffectiveModel();

    /**
     * Gets the profiles that were active during model building.
     *
     * @return The active profiles of the model or an empty list if the model has no active profiles.
     */
    @Nonnull
    List<Profile> getActivePomProfiles();

    /**
     * Gets the external profiles that were active during model building. External profiles are those that were

    /**
     * Gets the problems that were encountered during the settings building. Note that only problems of severity
     * {@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}
     */

    /**
     * Gets the problems that were encountered during the settings building. Note that only problems of severity
     * {@link BuilderProblem.Severity#WARNING} and below are reported here. Problems with a higher severity level cause
     * the settings builder to fail with a {@link ToolchainsBuilderException}.
     *
     * @return the problems that were encountered during the settings building, can be empty but never {@code null}
     */

    /**
     * Gets the problems that were encountered during the settings building. Note that only problems of severity
     * {@link SettingsProblem.Severity#WARNING} and below are reported here. Problems with a higher severity level cause
     * the settings builder to fail with a {@link SettingsBuildingException}.
     *
     * @return The problems that were encountered during the settings building, can be empty but never {@code null}.
     */

import java.nio.file.Path;

import org.apache.maven.api.annotations.Experimental;
import org.apache.maven.api.annotations.Immutable;

/**
 * An {@link Artifact} that is being produced by a {@link Project} during the build.
 *
 * <p>Produced artifacts includes:</p><ul>
 *     <li>{@linkplain Project#getPomArtifact() the project POM artifact}</li>
 *     <li>{@linkplain Project#getMainArtifact() the main artifact}</li>

import org.apache.maven.api.annotations.Nullable;
import org.apache.maven.api.services.MavenException;

/**
 * Represents an exception that occurs during the invocation of a Maven build or command.
 * This exception is typically thrown when there are errors during the execution of a Maven
 * process, such as build failures, plugin errors, or other runtime issues.
 *
 * @since 4.0.0
 */
@Experimental

     *
     * @return The decrypted proxy, can be empty but never {@code null}.
     */
    List<Proxy> getProxies();

    /**
     * Gets the problems that were encountered during the settings decryption.
     *
     * @return The problems that were encountered during the decryption, can be empty but never {@code null}.
     */
    List<SettingsProblem> getProblems();

     * @param parserRequest the request containing all necessary information for parsing
     * @return the parsed {@link MavenInvokerRequest}
     * @throws ParserException if there's an error during parsing of the request
     * @throws IOException if there's an I/O error during the parsing process
     */
    @Nonnull
    R parse(@Nonnull ParserRequest parserRequest) throws ParserException, IOException;