String path = System.getProperty(altLocationSysProp);

        if (path == null || path.isEmpty()) {
            // TODO This replacing shouldn't be necessary as user.home should be in the
            // context of the container and thus the value would be interpolated by Plexus
            String basedir = System.getProperty(basedirSysProp);
            if (basedir == null) {

that is possible for a user to perform in the UI we need to know the URI that is to be used with its given parameters. That URI in turn must map internally to a method in a given component which belongs to a plugin. This mapping should actually be more generalized and it shouldn’t matter internally whether this maps to the core application or extension of the application in the form of plugins.

In the short term we are working with the model where the URI maps to a resource, and the resource...

                        // MNG-2861: the artifact data has changed. If the available versions where previously
                        // retrieved, we need to update it.
                        // TODO shouldn't the versions be merged across relocations?
                        List<ArtifactVersion> available = artifact.getAvailableVersions();
                        if (available != null && !available.isEmpty()) {

            }

            // We do this in here so we can checksum the artifact metadata too, otherwise it could be metadata itself
            for (String extension : checksums.keySet()) {
                // TODO shouldn't need a file intermediary - improve wagon to take a stream
                File temp = File.createTempFile("maven-artifact", null);
                temp.deleteOnExit();

 * </p>
 * <p>
 * Wise voices have suggested that maybe aggregators shouldn't be bound to the ordinary
 * lifecycle at all, in which case we wouldn't be needing this class at all ( and
 * ProjectBuildList.getByTaskSegments). Or maybe they should be introduced in the calculation
 * of the execution plan instead, which seems much nicer.
 * </p>
 * <p>

  artifacts from invocation to invocation.

Maven Modifications

* DefaultPluginManager

  s/getMojoConfiguration()/getConfiguration()/g

  That should re-enable usage of mojo configuration. Ideally, we won't need any
  of the code that references this method, since the container should provide
  some way of recontextualizing the mojo, and all we would need to do is inject
  POM configuration via the lookup method or something.

 */
package org.apache.maven.execution;

/**
 * Describes whether a target should be activated or not, and if that is required or optional.
 */
enum ActivationSettings {
    ACTIVATION_OPTIONAL(true, true),
    ACTIVATION_REQUIRED(true, false),
    DEACTIVATION_OPTIONAL(false, true),
    DEACTIVATION_REQUIRED(false, false);

    /**
     * Should the target be active?
     */
    final boolean active;
    /**

     */
    MetadataResolutionRequest setRemoteRepositories(List<ArtifactRepository> remoteRepositories);

    /**
     * Determines whether the managed version information should be retrieved.
     *
     * @return {@code true} if the dependency management information should be retrieved, {@code false} otherwise.
     */
    boolean isResolveManagedVersions();

    /**

 *
 * @since 4.0.0
 */
@Experimental
@Immutable
public interface DependencyProperties {
    /**
     * Boolean flag telling that dependency contains all of its dependencies. Value of this key should be parsed with
     * {@link Boolean#parseBoolean(String)} to obtain value.
     * <p>
     * Important: this flag must be kept in sync with resolver! (as is used during collection)
     */

        return this;
    }

    /**
     * Gets the artifact filter that controls traversal of the dependency graph.
     *
     * @return The filter used to determine which of the artifacts in the dependency graph should be traversed or
     *         {@code null} to collect all transitive dependencies.
     */
    public ArtifactFilter getCollectionFilter() {
        return collectionFilter;
    }