public MetadataResolutionException() {
        // TODO Auto-generated constructor stub
    }

    public MetadataResolutionException(String message) {
        super(message);
        // TODO Auto-generated constructor stub
    }

    public MetadataResolutionException(Throwable cause) {
        super(cause);
        // TODO Auto-generated constructor stub
    }

import org.apache.maven.artifact.repository.metadata.RepositoryMetadataStoreException;

/**
 * Contains metadata about an artifact, and methods to retrieve/store it from an artifact repository.
 * TODO merge with artifactmetadatasource
 * TODO retrieval exception not appropriate for store
 *
 */
public interface ArtifactMetadata {
    /**
     * Whether this metadata should be stored alongside the artifact.
     *

    /**
     * Returns the default instance of the particular type of toolchain, can return <code>null</code>
     * if not applicable.
     * TODO keep around??
     **/
    ToolchainPrivate createDefaultToolchain();

/**
 * <p>
 * Provides the positional index of the project
 * </p>
 * <strong>NOTE:</strong> This class is not part of any public api and can be changed or deleted without prior notice.
 *
 * @since 3.0
 */
// TODO Kristian wonders if this class really is necessary and if it overlaps other concepts.
public final class ProjectIndex {

    private final Map<String, MavenProject> projects;

    private final Map<String, Integer> indices;

     * instance construction.
     *
     * @param session the Maven session
     * @throws MavenExecutionException in case of issue
     */
    // TODO This is too early for build extensions, so maybe just remove it?
    public void afterSessionStart(MavenSession session) throws MavenExecutionException {
        // do nothing
    }

    /**

                    null,
                    type.isIncludesDependencies(),
                    type.getLanguage().id(),
                    type.getPathTypes().contains(JavaPathType.CLASSES));
            // TODO: watch out for module path
        });

        // Note: here, type decides is artifact added to "build path" (for example during resolution)

import org.apache.maven.artifact.repository.layout.ArtifactRepositoryLayout2;

/**
 */
@Named
@Singleton
@Deprecated
public class DefaultArtifactRepositoryFactory implements ArtifactRepositoryFactory {
    // TODO use settings?
    private String globalUpdatePolicy;

    private String globalChecksumPolicy;

    @Inject
    private Map<String, ArtifactRepositoryLayout> repositoryLayouts;

import org.apache.maven.project.MavenProject;

/**
 * Wraps an active project instance to be able to receive updates from its artifact without affecting the original
 * attributes of this artifact.
 *
 * TODO I think this exposes a design flaw in that the immutable and mutable parts of an artifact are in one class and
 * should be split. ie scope, file, etc depend on the context of use, whereas everything else is immutable.
 */
@Deprecated

 * specific language governing permissions and limitations
 * under the License.
 */
package org.apache.maven.artifact;

/**
 * Exception that occurs when an artifact file is used, but has not been resolved.
 *
 * TODO it may be better for artifact.getFile() to throw it - perhaps it is a runtime exception?
 */
public class DependencyResolutionRequiredException extends Exception {
    public DependencyResolutionRequiredException(Artifact artifact) {

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

import java.util.List;

import org.apache.maven.artifact.Artifact;

/**
 * Filter to exclude from a list of artifact patterns.
 *
 * TODO I think this is equiv. to exclusion set filter in maven-core
 */
public class ExcludesArtifactFilter extends IncludesArtifactFilter {
    public ExcludesArtifactFilter(List<String> patterns) {
        super(patterns);
    }