getLongMessage(); public Object getSource(); } org/apache/maven/plugin/ContextEnabled.class package org.apache.maven.plugin; public abstract interface ContextEnabled { public abstract void setPluginContext(java.util.Map); public abstract java.util.Map getPluginContext(); } org/apache/maven/plugin/logging/Log.class package org.apache.maven.plugin.logging; public abstract interface Log { public abstract boolean isDebugEnabled(); public abstract void debug(CharSequence); public abstract void debug(CharSequence,...

 * TODO: add request trace so that requests can be linked together and through the resolver
 * TODO: add a Request interface holding session + parent request
 *
 * @since 4.0.0
 */
@Experimental
@ThreadSafe
public interface Session {

    @Nonnull
    Settings getSettings();

    @Nonnull
    LocalRepository getLocalRepository();

    @Nonnull

        this.pathTranslator = pathTranslator;
        this.urlNormalizer = urlNormalizer;
        this.rootLocator = rootLocator;
    }

    interface InnerInterpolator {
        String interpolate(String value);
    }

    @Override
    public Model interpolateModel(

                    session,
                    mojoDescriptor,
                    mojo.getClass(),
                    "Mojo implements `Contextualizable` interface from Plexus Container, which is EOL.");
        }

        XmlNode dom = mojoExecution.getConfiguration() != null
                ? mojoExecution.getConfiguration().getDom()
                : null;

 * TODO: replace validation level with an enum (though, we usually need just a boolean)
 *
 * @since 4.0.0
 */
@Experimental
@Immutable
public interface ModelBuilderRequest {

    /**
     * Denotes minimal validation of POMs. This validation level is meant for processing of POMs from repositories
     * during metadata retrieval.
     */

  reached or started.

  All of these operations will produce their own unique errors in the absence of
  a coordinated offline strategy. In addition, efforts to unite these failing
  behaviors behind a consistent user interface is much, much more difficult if
  the system can't tell whether it has access to the network required by these
  operations.

  Offline mode really means anticipating a lack of network connectivity, and as

    private void afterSessionEnd(MavenSession session) throws MavenExecutionException {
        callListeners(session, AbstractMavenLifecycleParticipant::afterSessionEnd);
    }

    @FunctionalInterface
    interface ListenerMethod {
        void run(AbstractMavenLifecycleParticipant listener, MavenSession session) throws MavenExecutionException;
    }

              <!-- internal field removed -->
              <exclude>org.apache.maven.graph.DefaultGraphBuilder#projectBuilder</exclude>
              <!-- MavenPluginValidator has been transformed into an interface -->
              <exclude>org.apache.maven.plugin.MavenPluginValidator</exclude>
              <!-- Remove plexus logger -->