_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)

/**
 * Information about the modules contained in a path element.
 * The path element may be a JAR file or a directory. Directories may use either package hierarchy
 * or module hierarchy, but not module source hierarchy. The latter is excluded because this class
 * is for path elements of compiled codes.
 */
class PathModularization {
    /**
     * A unique constant for all non-modular dependencies.
     */

 * 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
     */

                     * happens, add on class-path or module-path if allowed, or keep patching otherwise.
                     * The latter case (keep patching) is okay if the main module will be defined later.
                     */
                    type = cache.selectPathType(pathTypes, filter, path).orElse(type);
                }
                addPathElement(type, info.getKey());

); 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...

this is just a marker file....

                     * happens, add on class-path or module-path if allowed, or keep patching otherwise.
                     * The latter case (keep patching) is okay if the main module will be defined later.
                     */
                    type = cache.selectPathType(pathTypes, filter, path).orElse(type);
                }
                addPathElement(type, info.getKey());