static java.util.HashMap instances; private org.codehaus.plexus.classworlds.launcher.Configurator config; public static ConfiguratorAdapter getInstance(org.codehaus.plexus.classworlds.launcher.Configurator, Launcher); public static ConfiguratorAdapter getInstance(org.codehaus.plexus.classworlds.launcher.Configurator, ClassWorld); private void ConfiguratorAdapter(org.codehaus.plexus.classworlds.launcher.Configurator, Launcher); private void ConfiguratorAdapter(org.codehaus.plexus.classworlds.launcher.Configurator,...

org.hamcrest.Matcher<T> allOf(org.hamcrest.Matcher<? super T> first, org.hamcrest.Matcher<? super T> second) { return org.hamcrest.core.AllOf.<T>allOf(first, second); } /** * Creates a matcher that matches if the examined object matches <b>ALL</b> of the specified matchers. * <p/> * For example: * <pre>assertThat("myValue", allOf(startsWith("my"), containsString("Val")))</pre> */ public static <T> org.hamcrest.Matcher<T> allOf(org.hamcrest.Matcher<? super T> first, org.hamcrest.Matcher<? super T> second,...

import org.apache.maven.api.services.ProjectBuilder;
import org.apache.maven.api.services.ProjectBuilderRequest;
import org.apache.maven.api.services.SettingsBuilder;
import org.apache.maven.artifact.handler.manager.ArtifactHandlerManager;
import org.apache.maven.bridge.MavenRepositorySystem;
import org.apache.maven.execution.DefaultMavenExecutionRequest;
import org.apache.maven.execution.DefaultMavenExecutionResult;

static java.util.HashMap instances; private org.codehaus.plexus.classworlds.launcher.Configurator config; public static ConfiguratorAdapter getInstance(org.codehaus.plexus.classworlds.launcher.Configurator, Launcher); public static ConfiguratorAdapter getInstance(org.codehaus.plexus.classworlds.launcher.Configurator, ClassWorld); private void ConfiguratorAdapter(org.codehaus.plexus.classworlds.launcher.Configurator, Launcher); private void ConfiguratorAdapter(org.codehaus.plexus.classworlds.launcher.Configurator,...

        <type>test-jar</type>
        <scope>test</scope>
      </dependency>
      <dependency>
        <groupId>org.sonatype.plexus</groupId>
        <artifactId>plexus-plugin-manager</artifactId>
        <version>${plexusPluginManagerVersion}</version>
      </dependency>
      <!--start-->
      <dependency>
        <groupId>easymock</groupId>
        <artifactId>easymock</artifactId>

        <type>test-jar</type>
        <scope>test</scope>
      </dependency>
      <dependency>
        <groupId>org.sonatype.plexus</groupId>
        <artifactId>plexus-plugin-manager</artifactId>
        <version>${plexusPluginManagerVersion}</version>
      </dependency>
      <!--start-->
      <dependency>
        <groupId>easymock</groupId>
        <artifactId>easymock</artifactId>

// 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
// the structure I want to test by using the artifact handler manager which dictates
// the layout used for a particular artifact type.

/**
 */
@Deprecated
class ArtifactResolverTest extends AbstractArtifactComponentTestCase {
    @Inject

            if (artifact.isSnapshot()) {
                Matcher matcher = Artifact.VERSION_FILE_PATTERN.matcher(artifact.getVersion());
                if (matcher.matches()) {
                    Snapshot snapshot = new Snapshot();
                    snapshot.setTimestamp(matcher.group(2));
                    try {
                        snapshot.setBuildNumber(Integer.parseInt(matcher.group(3)));

import org.eclipse.aether.internal.impl.scope.ScopeDependencySelector;
import org.eclipse.aether.internal.impl.scope.ScopeManagerImpl;
import org.eclipse.aether.repository.LocalRepository;
import org.eclipse.aether.util.graph.manager.ClassicDependencyManager;
import org.eclipse.aether.util.graph.selector.AndDependencySelector;
import org.eclipse.aether.util.graph.selector.ExclusionDependencySelector;

  NOTE: One side-effect of this design change is that all offline-mode code can
  be isolated to maven-core, maven-plugin-descriptor, and [possibly]
  maven-artifact. Usage of maven-wagon will be determined by an offline-aware
  manager.

* Assumptions: What is Offline?

  For the purposes of determining the areas sensitive to offline status,
  it is definitely useful to define what the offline state really means.