their projects. It also allows for a certain amount of legacy support into the
  future. Therefore, we should rename this file from pom.xml in the maven-core
  jarfile to pom-4.0.0.xml (and successive revisions to the base pom made to
  accommodate changes in the model will be named accordingly - 4.0.1, 4.0.2, ...).

Minimum Element-Set for a Project POM

  In order to furnish a basic set of information which we need to distinguish one

 * registered component descriptors twice: once keyed by role+roleHint and once keyed by role only. This effectively
 * made the metadata source available with its original role hint ("maven") as well as the default hint.
 *
 */
@Named
@Singleton
@Deprecated
public class DefaultMetadataSource extends MavenMetadataSource {
    @Inject

     * verify the path and resolve the artifact if the path actually denotes an existing file. If the path isn't valid,
     * resolution will fail and no attempts to search local/remote repositories are made.
     */
    public static final String LOCAL_PATH = "localPath";

    private MavenArtifactProperties() {
        // hide constructor
    }

        } catch (IOException e) {
            LOGGER.warn("Unable to read {}. The --resume / -r feature will not work.", path);
        }

        return properties;
    }

    // This method is made package-private for testing purposes
    void applyResumptionProperties(MavenExecutionRequest request, Properties properties) {
        String str1 = request.getResumeFrom();

        msgs.add("* as @threadSafe to support parallel building.                  *");
        msgs.add("* While this /may/ work fine, please look for plugin updates    *");
        msgs.add("* and/or request plugins be made thread-safe.                   *");
        msgs.add("* If reporting an issue, report it against the plugin in        *");
        msgs.add("* question, not against maven-core                              *");

import org.apache.maven.artifact.repository.ArtifactRepository;

/**
 * A simple recording of the Artifacts that could not be resolved for a given resolution request, along with
 * the remote repositories where attempts were made to resolve the artifacts.
 *
 */
@Deprecated
public class UnresolvedArtifacts {
    private Artifact originatingArtifact;

    private List<Artifact> artifacts;

    and match them against the toolchain requirements of the project (as configured in {@code pom.xml}):
    if match is found, the toolchain instance is made available to other Maven plugins.</p>
    <p>With {@code jdk} toolchain, for example, instead of being stuck with the JDK used to run Maven, all plugins can use

/**
 *
 * Note: uses @Typed to limit the types it is available for injection to just ModelProcessor.
 *
 * This is because the ModelProcessor interface extends ModelLocator and ModelReader. If we
 * made this component available under all its interfaces then it could end up being injected
 * into itself leading to a stack overflow.
 *
 * A side effect of using @Typed is that it translates to explicit bindings in the container.

        </goals>
      </execution>
    </executions>
  </plugin>
  .
  .
  .
</plugins>

 JAR plugin as well as its dependencies. The realms noted above are setup
 in a hierarchical structure where the resources in the parent realms are
 available but the <<realm is searched first before a search is made in
 the parent realm>>.

 Plugins are guaranteed to be provided the resources found in
 <<<plexus.core>>> and <<<plexus.core.maven>>> realms at run-time if required.