import org.apache.maven.model.version.ModelVersionParser;

import static org.apache.maven.internal.impl.Utils.nonNull;

/**
 * A wrapper class around a resolver version that works as model version parser as well.
 */
@Named
@Singleton
public class DefaultVersionParser implements VersionParser {
    private final ModelVersionParser modelVersionParser;

    @Inject

     *
     * @param remoteRepository the repository
     */
    void setRepository(ArtifactRepository remoteRepository);

    /**
     * Get the repository metadata associated with this marker.
     *
     * @return the metadata, or <code>null</code> if none loaded
     */
    Metadata getMetadata();

    /**
     * Set the metadata contents.
     *
     * @param metadata the metadata
     */

     *
     * @param dir the directory to locate the pom for, never {@code null}
     * @return a {@code Source} pointing to the located pom or an empty {@code Optional} if none was found by this parser
     */
    @Nonnull
    Optional<Source> locate(@Nonnull Path dir);

    /**
     * Parse the model obtained previously by a previous call to {@link #locate(Path)}.
     *

    protected File getLocalRepositoryPath() throws FileNotFoundException, URISyntaxException {
        File markerFile = getFileForClasspathResource("local-repo/marker.txt");

        return markerFile.getAbsoluteFile().getParentFile();
    }

    protected static File getFileForClasspathResource(String resource)
            throws FileNotFoundException, URISyntaxException {

_dont_implement_Matcher___instead_extend_BaseMatcher_() Deprecated. Description copied from interface: Matcher This method simply acts a friendly reminder not to implement Matcher directly and instead extend BaseMatcher. It's easy to ignore JavaDoc, but a bit harder to ignore compile errors . Specified by: _dont_implement_Matcher___instead_extend_BaseMatcher_ in interface Matcher<T> See Also: Matcher._dont_implement_Matcher___instead_extend_BaseMatcher_() describeMismatch public void describeMismatch(java.lang.Object...

 maven.multiproject.includes property.
 2. it works without problems only for projects with relative paths, e.g., from
 one CVS repository.. for projects from multiple SCM repositories it's harder
 to maintain the same relative links on all developer computers.
 not sure the unified source directory structure addresses this issue.

 Properties

 maven.user.config.dir (system,default=${user.home}/.m2)

 * prior notice.
 *
 */
public interface PluginArtifactsCache {

    /**
     * A cache key.
     */
    interface Key {
        // marker interface for cache keys
    }

    /**
     * CacheRecord
     */
    class CacheRecord {

        private final List<Artifact> artifacts;

        public List<Artifact> getArtifacts() {

 * prior notice.
 *
 */
public interface ProjectArtifactsCache {

    /**
     * A cache key.
     */
    interface Key {
        // marker interface for cache keys
    }

    interface ArtifactsSetWithResult extends Set<Artifact> {
        DependencyResolutionResult getResult();
    }

    /**
     * CacheRecord
     */

); public void setValue(String); public void setLine(String); public void setFile(java.io.File); public String[] getParts(); } org/codehaus/plexus/util/cli/Commandline$Marker.class package org.codehaus.plexus.util.cli; public synchronized class Commandline$Marker { private int position; private int realPos; void Commandline$Marker(Commandline, int); public int getPosition(); } org/codehaus/plexus/util/cli/Commandline.class package org.codehaus.plexus.util.cli; public synchronized class Commandline...

                        continue;
                    }
                    subdir = path;
                }
                // When the same module is found in main and test output, the latter is patching the former.
                addPathElement(JavaPathType.patchModule(moduleName), subdir);
                addToClasspath = false;
            }
            /*