setEnabled(String.valueOf(enabled));
    }

            ]]>
          </code>
        </codeSegment>
      </codeSegments>
    </class>

    <!--@todo find better solution for management of site deployments -->
    <class>
      <name>Site</name>
      <version>4.0.0+</version>
      <description>Contains the information needed for deploying websites.</description>

 * under the License.
 */
package org.apache.maven.artifact.resolver.filter;

import java.util.Objects;

/**
 * Filter to only retain objects in the given artifactScope or better.
 *
 */
public class ScopeArtifactFilter extends AbstractScopeArtifactFilter {

    private final String scope;

    public ScopeArtifactFilter(String scope) {
        this.scope = scope;

                            resolved = conflictResolver.resolveConflict(previous, node);
                        }

                        if (resolved == null) {
                            // TODO add better exception that can detail the two conflicting artifacts
                            ArtifactResolutionException are = new ArtifactResolutionException(

 */
package org.apache.maven.artifact.resolver.filter;

import java.util.Collection;
import java.util.HashSet;
import java.util.Set;

/**
 * Filter to only retain objects in the given scope or better. This implementation allows the accumulation of multiple
 * scopes and their associated implied scopes, so that the user can filter apply a series of implication rules in a

        session.setAllProjects(session.getProjects());
        session.setSession(defaultSessionFactory.newSession(session));

        SessionScope sessionScope = getContainer().lookup(SessionScope.class);
        sessionScope.enter();
        sessionScope.seed(MavenSession.class, session);
        sessionScope.seed(Session.class, session.getSession());
        sessionScope.seed(InternalMavenSession.class, InternalMavenSession.from(session.getSession()));

    <version>4.0.0-beta-1-SNAPSHOT</version>
  </parent>

  <artifactId>maven-api</artifactId>
  <packaging>pom</packaging>
  <name>Maven 4 API</name>
  <description>A new immutable API for Maven 4 to better manage what plugins and extensions can influence.</description>

  <modules>
    <module>maven-api-meta</module>
    <module>maven-api-di</module>
    <module>maven-api-xml</module>
    <module>maven-api-model</module>

        }

        //
        // We enter the session scope right after the MavenSession creation and before any of the
        // AbstractLifecycleParticipant lookups
        // so that @SessionScoped components can be @Injected into AbstractLifecycleParticipants.
        //
        sessionScope.enter();
        MavenChainedWorkspaceReader chainedWorkspaceReader =

        Thread.currentThread().setContextClassLoader(pluginRealm);

        MavenSession oldSession = legacySupport.getSession();

        scope.enter();

        try {
            scope.seed(MavenProject.class, project);
            scope.seed(MojoExecution.class, mojoExecution);
            scope.seed(
                    org.apache.maven.api.plugin.Log.class,

        logger.debug(indent + artifact + " (not setting artifactScope to: " + ignoredScope + "; local artifactScope "
                + artifact.getScope() + " wins)");

        // TODO better way than static? this might hide messages in a reactor
        if (!ignoredArtifacts.contains(artifact)) {
            logger.warn("\n\tArtifact " + artifact + " retains local artifactScope '" + artifact.getScope()

  repositories are "really" offline, since offline mode is more of a behavior,
  and this will lead to counter-intuitive results. A different feature may exist
  unimplemented, which is to detect when the network is down and provide better
  feedback for that case. However, when offline mode is declared, nothing
  earmarked as remote should be accessed, regardless of whether it is actually
  a physically local resource.