various sources must be consolidated and injected using the container.

  Currently, mojo configuration is done externally to the container, in the
  DefaultPluginManager in the maven-core API. In order to get from here to
  there, we need to do several things to add capability to the default
  configuration of plexus. This document will detail those changes.

Container Enhancements

* ExpressionEvaluator

    <artifactId>plexus-containers</artifactId>
    <groupId>org.codehaus.plexus</groupId>
    <version>1.0-alpha-16</version>
  </parent>
  <modelVersion>4.0.0</modelVersion>
  <artifactId>plexus-container-default</artifactId>
  <name>Default Plexus Container</name>
  <version>1.0-alpha-16</version>
  <build>
    <plugins>
      <plugin>
        <artifactId>maven-surefire-plugin</artifactId>
        <configuration>

  <parent>
    <groupId>org.codehaus.plexus</groupId>
    <artifactId>plexus-containers</artifactId>
    <version>1.0-alpha-32</version>
  </parent>
  <artifactId>plexus-container-default</artifactId>
  <name>Default Plexus Container</name>
  <version>1.0-alpha-32</version>
  <build>
    <plugins>
      <plugin>
        <artifactId>maven-surefire-plugin</artifactId>
        <configuration>

     * This map is usually either empty if no module was found, or a singleton map.
     * It may however contain more than one entry if module hierarchy was detected,
     * in which case there is one key per sub-directory.
     *
     * <p>This map may contain null values if the constructor was invoked with {@code resolve}
     * parameter set to false. This is more efficient when only the module existence needs to

Object[] toArray(Object[]); } META-INF/maven/org.codehaus.plexus/plexus-active-collections/pom.xml 4.0.0 plexus-components org.codehaus.plexus 1.1.6 plexus-active-collections 1.0-beta-1 Plexus Container-Backed Active Collections org.codehaus.plexus plexus-component-api 1.0-alpha-16 org.codehaus.plexus plexus-container-default 1.0-alpha-16 junit junit 3.8.1 test maven-surefire-plugin **/TestComponent.java **/TestBadComponent.java **/*TCK.java scm:svn:https://svn.codehaus.org/plexus/tags/plexus-active-c...

Guillaume Nodet <******@****.***> 1664700085 +0200

Guillaume Nodet <******@****.***> 1664700085 +0200

the current Thread context class loader (if there is one), or from the class loader that loaded the LogFactory class itself otherwise. This allows a copy of commons-logging.jar to be shared in a multiple class loader environment (such as a servlet container), but still allow each web application to provide its own LogFactory implementation, if it so desires. An instance of this class will then be created, and cached per class loader. The Default LogFactory Implementation The Logging Package APIs include...

        PlexusContainer container = getContainer();

        ComponentDescriptor<T> cd = new ComponentDescriptor<>(participant, container.getContainerRealm());
        cd.setRoleClass(AbstractMavenLifecycleParticipant.class);
        container.addComponentDescriptor(cd);

        Maven maven = container.lookup(Maven.class);
        File pom = getProject(testProject);

@Named
@Singleton
public class DefaultCoreRealm implements CoreRealm {

    private final PlexusContainer container;

    @Inject
    public DefaultCoreRealm(PlexusContainer container) {
        this.container = container;
    }

    @Override
    public ClassRealm getRealm() {
        return container.getContainerRealm();
    }