this.lookup = requireNonNull(lookup);
        this.defaultLifeCycles = requireNonNull(defaultLifeCycles);
    }

    // These methods deal with construction intact Plugin object that look like they come from a standard
    // <plugin/> block in a Maven POM. We have to do some wiggling to pull the sources of information
    // together and this really shows the problem of constructing a sensible default configuration but

        }
    }

    /**
     * Wraps an object, providing reflective access to the object graph of which the
     * supplied object is the root. Expressions like 'child.name' will translate into
     * 'rootObject.getChild().getName()' for non-boolean properties, and
     * 'rootObject.getChild().isName()' for boolean properties.
     */

        return request.getUserProperties();
    }

    /**
     * Gets the system properties to use for interpolation and profile activation. The system properties are collected
     * from the runtime environment like {@link System#getProperties()} and environment variables.
     *
     * @return The system properties, never {@code null}.
     */
    public Properties getSystemProperties() {

  implementation of the BasicComponentConfigurator. This ExpressionEvaluator
  simply returns the expression itself as the resolved value, which adds
  very little value to the container. Things like ${project.build.resources}
  are not resolved, and result in a type mismatch for the member injection.

  We need a replacement for DefaultExpressionEvaluator that is capable of

        </field>
        <field>
          <name>configuration</name>
          <version>1.0.0+</version>
          <type>DOM</type>
          <description>
            Toolchain configuration information, like location or any information that is to be retrieved.
            &lt;p>Actual content structure is completely open: each toolchain type will define its own format and
            semantics.

  |
  | o validators: there could be several levels of validation. Simple type validation could
  |   be done with a regex, but we need inter-field validation and rules which could be
  |   dealt with by something like drools.
  |
  | o i18n: would be good to be able to have names/descriptions/specifications
  |   in as many languages as possible. (see MNG-3626)
  |

    <commonsCliVersion>1.0</commonsCliVersion>
    <!--

    Do not update this, Doxia will be decoupled completely from 3.x and someone can
    create a rendering engine for it if they like when the release stabilizes. JVZ

    -->
    <doxiaVersion>1.0-alpha-9</doxiaVersion>
    <easyMockVersion>1.2_Java1.3</easyMockVersion>
    <junitVersion>4.13.1</junitVersion>

     */
    @Nonnull
    RemoteRepository createRemoteRepository(@Nonnull Repository repository);

    /**
     * Creates a coordinate out of string that is formatted like:
     * {@code <groupId>:<artifactId>[:<extension>[:<classifier>]]:<version>}.
     * <p>
     * Shortcut for {@code getService(ArtifactFactory.class).create(...)}.
     *

        ArtifactResolutionResult result = new ArtifactResolutionResult();

        // The root artifact may, or may not be resolved so we need to check before we attempt to resolve.
        // This is often an artifact like a POM that is taken from disk and we already have hold of the
        // file reference. But this may be a Maven Plugin that we need to resolve from a remote repository
        // as well as its dependencies.

                            child.addDependencies(rGroup.getArtifacts(), rGroup.getResolutionRepositories(), filter);

                        } catch (CyclicDependencyException e) {
                            // would like to throw this, but we have crappy stuff in the repo

                            fireEvent(
                                    ResolutionListener.OMIT_FOR_CYCLE,
                                    listeners,