* to process and store tracking information ONLY into local repository, not to any other place. This method
     * filters out currently built artifacts, as events are fired for them as well, but their resolved artifact
     * file would point to checked out source-tree, not the local repository.
     * <p>
     * Visible for testing.
     */
    static boolean isLocalRepositoryArtifactOrMissing(RepositorySystemSession session, Artifact artifact) {

    public Artifact getArtifact() {
        return artifact;
    }

    public void setArtifact(Artifact artifact) {
        this.artifact = artifact;
    }

    // TODO I would like to get rid of this. jvz.
    public Model getModel() {
        return model;
    }

    /**
     * Returns the project corresponding to a declared parent.
     *

import static org.junit.jupiter.api.Assertions.assertEquals;
import static org.junit.jupiter.api.Assertions.assertThrows;
import static org.junit.jupiter.api.Assertions.assertTrue;

// It would be cool if there was a hook that I could use to set up a test environment.
// I want to set up a local/remote repositories for testing but I don't want to have
// to change them when I change the layout of the repositories. So I want to generate

void <clinit>(); } org/codehaus/plexus/util/xml/pull/XmlPullParserExcepti.class package org.codehaus.plexus.util.xml.pull; public synchronized class XmlPullParserExcepti extends Exception { protected Throwable detail; protected int row; protected int column; public void XmlPullParserExcepti(String); public void XmlPullParserExcepti(String, XmlPullParser, Throwable); public Throwable getDetail(); public int getLineNumber(); public int getColumnNumber(); public void printStackTrace(); } org/codehaus/p...

void <clinit>(); } org/codehaus/plexus/util/xml/pull/XmlPullParserExcepti.class package org.codehaus.plexus.util.xml.pull; public synchronized class XmlPullParserExcepti extends Exception { protected Throwable detail; protected int row; protected int column; public void XmlPullParserExcepti(String); public void XmlPullParserExcepti(String, XmlPullParser, Throwable); public Throwable getDetail(); public int getLineNumber(); public int getColumnNumber(); public void printStackTrace(); } org/codehaus/p...

     * @return The populated execution request, never {@code null}.
     * @throws MavenExecutionRequestPopulationException If the execution request could not be populated.
     * @since 3.3.0
     */
    MavenExecutionRequest populateFromToolchains(MavenExecutionRequest request, PersistedToolchains toolchains)
            throws MavenExecutionRequestPopulationException;

        super("The POM expression: " + expression + " could not be evaluated. Reason: " + message, cause);

        this.expression = expression;
        this.originalMessage = message;
    }

    public ModelInterpolationException(String expression, String message) {
        super("The POM expression: " + expression + " could not be evaluated. Reason: " + message);

        this.expression = expression;

     * @return The version result, never {@code null}.
     * @throws VersionResolverException If the metaversion could not be resolved.
     */
    @Nonnull
    default VersionResolverResult resolve(@Nonnull Session session, @Nonnull ArtifactCoordinate artifactCoordinate)
            throws VersionResolverException {

    // to validate the properties. We also need a way to navigate from the Tex specification documents to
    // the test in question and vice versa. A little Eclipse plugin would do the trick.
    public void testThatExecutionsWithoutIdsAreMergedAndTheChildWins() throws Exception {
        PomTestWrapper tester = buildPom("micromailer");

     * @return The resolved plugin artifact, never {@code null}.
     * @throws PluginResolutionException If the plugin artifact could not be resolved.
     */
    Artifact resolve(Plugin plugin, List<RemoteRepository> repositories, RepositorySystemSession session)
            throws PluginResolutionException;

    /**