public MetadataResolutionException() {
        // TODO Auto-generated constructor stub
    }

    public MetadataResolutionException(String message) {
        super(message);
        // TODO Auto-generated constructor stub
    }

    public MetadataResolutionException(Throwable cause) {
        super(cause);
        // TODO Auto-generated constructor stub
    }

import org.apache.maven.lifecycle.internal.stub.BuildPluginManagerStub;
import org.apache.maven.lifecycle.internal.stub.DefaultLifecyclesStub;
import org.apache.maven.lifecycle.internal.stub.PluginPrefixResolverStub;
import org.apache.maven.lifecycle.internal.stub.PluginVersionResolverStub;
import org.apache.maven.lifecycle.internal.stub.ProjectDependencyGraphStub;

 */
package org.apache.maven.lifecycle.internal;

import java.util.List;

import org.apache.maven.lifecycle.MavenExecutionPlan;
import org.apache.maven.lifecycle.internal.stub.LifecycleExecutionPlanCalculatorStub;
import org.apache.maven.lifecycle.internal.stub.ProjectDependencyGraphStub;
import org.apache.maven.plugin.MojoExecution;
import org.junit.jupiter.api.Test;

import static org.junit.jupiter.api.Assertions.assertFalse;

     * @throws NTLMEngineException if an NTLM engine error occurs.
     */
    @Override
    public String generateType1Msg(final String arg0, final String arg1) throws NTLMEngineException {
        // TODO Auto-generated method stub
        return null;
    }

    /**
     * Generates a Type 3 NTLM message.
     * @param username The username.
     * @param password The password.
     * @param domain The domain.

 * KIND, either express or implied.  See the License for the
 * specific language governing permissions and limitations
 * under the License.
 */
package org.apache.maven.lifecycle.internal.stub;

import java.util.ArrayList;
import java.util.Arrays;
import java.util.List;

import org.apache.maven.execution.AbstractExecutionListener;
import org.apache.maven.execution.DefaultMavenExecutionRequest;

and can be asserted as desired.

You can change/extend these stubs, and tests should not be breaking too much, since most tests
assert using expected values from the stubs. Normally, when you try to use data from the stubs that
have not been properly populated, you'll get a nullpointer in your test and you then have to
identify which stub creates that specific piece of data.

The most important stubs are:
LifecycleExecutionPlanCalculatorStub

import org.apache.maven.execution.MavenSession;
import org.apache.maven.lifecycle.LifecycleExecutionException;
import org.apache.maven.lifecycle.internal.stub.MojoExecutorStub;
import org.apache.maven.lifecycle.internal.stub.ProjectDependencyGraphStub;
import org.apache.maven.plugin.MojoExecution;
import org.apache.maven.project.MavenProject;
import org.codehaus.plexus.PlexusContainer;

        }
    }
    
    public WitnessRegisterResponse register(WitnessRegisterRequest request) throws IOException {
        try {
            WitnessRegisterStub stub = new WitnessRegisterStub(request);
            handle.sendrecv(stub);
            return stub.getResponse();
        } catch (Exception e) {
            throw new IOException("Witness register RPC failed", e);
        }
    }
    

-->

<project>
  <modelVersion>4.0.0</modelVersion>

  <groupId>org.apache.maven</groupId>
  <artifactId>standalone-pom</artifactId>
  <version>1</version>
  <packaging>pom</packaging>
  <name>Maven Stub Project (No POM)</name>

     */
    @Nonnull
    Optional<Source> getSource();

    /**
     * Determines whether a stub model should be allowed when the POM is missing or unreadable.
     * A stub model contains only minimal information derived from the project's coordinates.
     *
     * @return true if a stub model should be allowed, false otherwise
     */
    boolean isAllowStubModel();

    /**