~~ KIND, either express or implied.  See the License for the
~~ specific language governing permissions and limitations
~~ under the License.

  ---
  Getting to Plexus-configured Mojos
  ---
  John Casey
  ---
  2005-04-29

Abstract

  We're moving toward integrating mojos as first-class plexus components, while

 * Builds the toolchains model from a previously configured filesystem path to the toolchains file.
 * <strong>Note:</strong> This is an internal component whose interface can change without prior notice.
 *
 * @deprecated use {@link org.apache.maven.toolchain.building.ToolchainsBuilder} instead
 */
@Deprecated
public interface ToolchainsBuilder {

    /**
     * Builds the toolchains model from the configured toolchain files.
     *

     * Maven-based resolution. In more detail, this method configures settings relevant for the processing of dependency
     * graphs, most other settings remain at their generic default value. Use the various setters to further configure
     * the session with authentication, mirror, proxy and other information required for your environment. At least,
     * local repository manager needs to be configured to make session be able to create session instance.
     *

     */
    Properties getSystemProperties();

    /**
     * Sets the user properties to use for interpolation and profile activation. The user properties have been
     * configured directly by the user on his discretion, e.g. via the {@code -Dkey=value} parameter on the command
     * line.
     *
     * @param userProperties The user properties, may be {@code null}.

                if (!repositories.isEmpty()) {
                    trackingData.add("Configured repositories:");
                    for (RemoteRepository r : repositories) {
                        trackingData.add(" - " + r.getId() + " : " + r.getUrl());
                    }
                } else {
                    trackingData.add("No repositories configured");
                }
            }

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

/**
 * Thrown when a bean couldn't be configured.
 *
 */
public class BeanConfigurationException extends Exception {

    public BeanConfigurationException(String message) {
        super(message);
    }

     */
    Map<String, String> getSystemProperties();

    /**
     * Gets the user properties to use for interpolation and profile activation. The user properties have been
     * configured directly by the user on his discretion, e.g. via the {@code -Dkey=value} parameter on the command
     * line.
     *
     * @return The user properties, never {@code null}.
     */

import org.apache.maven.wagon.providers.file.FileWagon;

/**
 * Mock of a Wagon for testing
 *
 */
public class WagonMock extends FileWagon {

    /**
     * A field that can be configured in the Wagon
     *
     * @component.configuration default="configurableField"
     */
    private String configurableField = null;

    public void setConfigurableField(String configurableField) {

 * the fact that the problem reporter has/should not have information about the calling context and hence cannot provide
 * an expressive source hint for the model problem. Instead, the source hint is configured by the model builder before
 * it delegates to other components that potentially encounter problems. Then, the problem reporter can focus on

import java.util.Map;
import java.util.Properties;

import org.apache.maven.api.Session;
import org.apache.maven.api.annotations.Nullable;

/**
 * Centralized class for Maven Core feature information.
 * Features configured are supposed to be final in a given maven session.
 *
 * @since 4.0.0
 */
public final class Features {

    /**
     * Name of the Maven user property to enable or disable the build/consumer POM feature.