<dependency>
      <groupId>org.apache.maven</groupId>
      <artifactId>maven-model</artifactId>
    </dependency>
    <dependency>
      <groupId>org.apache.maven</groupId>
      <artifactId>maven-artifact</artifactId>
    </dependency>
    <dependency>
      <groupId>com.fasterxml.woodstox</groupId>
      <artifactId>woodstox-core</artifactId>
    </dependency>
    <dependency>

import org.apache.maven.api.annotations.Immutable;
import org.apache.maven.api.annotations.Nonnull;
import org.apache.maven.api.annotations.Nullable;

/**
 * {@code ArtifactCoordinates} completed with information about how the artifact will be used.
 * This information include the dependency type (main classes, test classes, <i>etc.</i>),
 * a scope (compile-time, run-time <i>etc.</i>), an obligation (whether the dependency

    <artifactId>maven</artifactId>
    <version>4.0.0-beta-6-SNAPSHOT</version>

    <relativePath>../../</relativePath>
  </parent>

  <artifactId>maven-resolver-provider</artifactId>

  <name>Maven Artifact Resolver Provider (deprecated)</name>
  <description>Extensions to Maven Resolver for utilizing Maven POM and repository metadata.</description>

  <dependencies>
    <dependency>
      <groupId>org.apache.maven</groupId>

 *   <li>In at least one case, a use of {@code sun.misc.FpUtils}, the test will not even
 *       <i>compile</i> against Android. Now, this might be an artifact of our build system, one
 *       that we could probably work around. Or we could manually strip the test from open-source
 *       Guava while continuing to run it internally, as we do with many other tests. This would

import org.apache.maven.api.settings.Settings;
import org.apache.maven.artifact.InvalidRepositoryException;
import org.apache.maven.artifact.repository.ArtifactRepository;
import org.apache.maven.artifact.repository.ArtifactRepositoryPolicy;
import org.apache.maven.artifact.repository.MavenArtifactRepository;
import org.apache.maven.artifact.repository.layout.DefaultRepositoryLayout;
import org.apache.maven.bridge.MavenRepositorySystem;

import org.apache.maven.api.services.Lookup;
import org.apache.maven.api.services.LookupException;
import org.apache.maven.api.services.MavenException;
import org.apache.maven.api.settings.Settings;
import org.apache.maven.artifact.repository.ArtifactRepository;
import org.apache.maven.bridge.MavenRepositorySystem;
import org.apache.maven.execution.MavenSession;
import org.apache.maven.plugin.MojoExecution;

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

/**
 * Authentication
 */
public class Authentication {

    private String privateKey;

    private String passphrase;

    public Authentication(String userName, String password) {

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

/**
 * Describes a restriction in versioning.
 *
 */
public class Restriction {
    private final ArtifactVersion lowerBound;

    private final boolean lowerBoundInclusive;

import javax.inject.Named;
import javax.inject.Singleton;

import java.net.MalformedURLException;
import java.net.URL;
import java.util.List;

import org.apache.maven.RepositoryUtils;
import org.apache.maven.artifact.repository.ArtifactRepository;
import org.apache.maven.settings.Mirror;

/**
 * DefaultMirrorSelector
 */
@Named
@Singleton
public class DefaultMirrorSelector implements MirrorSelector {

  <id>lifecycle</id>
  <name>Lifecycle</name>
  <description>
    Configuration of custom lifecycle mappings for the plugin, as generally stored in
    {@code META-INF/maven/lifecycle.xml} in a plugin's jar artifact.
  </description>
  <classes>
    <class rootElement="true" xml.tagName="lifecycles" xsd.compositor="sequence">
      <name>LifecycleConfiguration</name>
      <version>1.0.0+</version>