resource itself is a Plexus component which can itself have a reference to the host application in order to perform its work. This may not occur in the first versions of the plugin API but a resource needs to simply become the mapping mechanism by which parameters are taken from the REST side of the application and mapped into a method call within a given Plexus component. Whether that be the core Nexus application or a component provided by a plugin.

At the very least in the short term...

you really will want to review the remainder of this page in order to understand how to configure logging for your application. Configuring the Commons Logging Package Choosing a LogFactory Implementation From an application perspective, the first requirement is to retrieve an object reference to the LogFactory instance that will be used to create Log instances for this application. This is normally accomplished by calling the static getFactory() method. This method implements the following discovery...

  <parent>
    <groupId>org.sonatype.mavenbook.multi</groupId>
    <artifactId>simple-parent</artifactId>
  </parent>

  <artifactId>simple-webapp</artifactId>
  <name>Multi Chapter Simple Web Application Project</name>
  <dependencies>
    <dependency>
      <groupId>org.sonatype.mavenbook.multi</groupId>
      <artifactId>simple-weather</artifactId>
    </dependency>
  </dependencies>
  <build>

    @SuppressWarnings("checkstyle:linelength")
    private static final String[] BINDINGS = {
        "generate-resources",
                "org.apache.maven.plugins:maven-ear-plugin:" + EAR_PLUGIN_VERSION + ":generate-application-xml",
        "process-resources",
                "org.apache.maven.plugins:maven-resources-plugin:" + RESOURCES_PLUGIN_VERSION + ":resources",

            ^
            |
   [plexus.core.maven]
     ^            ^
     |            |
[plugin0]      [plugin1]
+-----+

 The <<<plexus.core>>> realm contains the resources required to run any
 plexus application; The <<<plexus.core.maven>>> realm contains all of the
 resources required to run Maven. Each subsequent plugin realm contains the
 JAR plugin as well as its dependencies. The realms noted above are setup

you really will want to review the remainder of this page in order to understand how to configure logging for your application. Configuring the Commons Logging Package Choosing A LogFactory Implementation From an application perspective, the first requirement is to retrieve an object reference to the LogFactory instance that will be used to create Log instances for this application. This is normally accomplished by calling the static getFactory() method. This method implements the following discovery...

  <groupId>test</groupId>
  <artifactId>test</artifactId>
  <version>0.1-SNAPSHOT</version>
  <packaging>pom</packaging>

  <modules>
    <module>lib</module> <!-- the library -->
    <module>app</module> <!-- the application -->
  </modules>

  <build>
    <pluginManagement>
      <plugins>
        <plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-compiler-plugin</artifactId>

 * under the License.
 */
package org.apache.maven.execution;

import org.apache.maven.artifact.versioning.ArtifactVersion;

/**
 * Describes runtime information about the application.
 *
 * @deprecated Use {@link org.apache.maven.rtinfo.RuntimeInformation} instead.
 */
@Deprecated
public interface RuntimeInformation {
    ArtifactVersion getApplicationVersion();

import org.codehaus.plexus.personality.plexus.lifecycle.phase.Initializable;
import org.codehaus.plexus.personality.plexus.lifecycle.phase.InitializationException;

/**
 * Describes runtime information about the application.
 *
 */
@Deprecated
@Named
@Singleton
public class DefaultRuntimeInformation implements RuntimeInformation, Initializable {

    @Inject
    private org.apache.maven.rtinfo.RuntimeInformation rtInfo;

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

import org.apache.maven.artifact.Artifact;

/**
 * This exception is thrown if an application attempts to attach
 * two of the same artifacts to a single project.
 *
 * TODO Make this a checked exception, and modify the API of MavenProjectHelper.