<!-- localRepository
   | The path to the local repository maven will use to store artifacts.
   |
   | Default: ${user.home}/.m2/repository
  <localRepository>/path/to/local/repo</localRepository>
  -->

  <!-- interactiveMode
   | This will determine whether maven prompts you when it needs input. If set to false,
   | maven will use a sensible default value, perhaps based on some other setting, for

 Plugins can state compile-time dependencies on any of the resources found in
 the core realms listed above and these dependencies will be included in the
 plugin descriptor that is generated but when running within Maven these
 resources will be filtered out. In other words these resources will not
 be added the realm created for the plugins execution as they are provided

h3. Plugins need a specific metadata model

Each application will have its own model for plugins. Much of this model will be common across applications but there will always be issues specific to a particular applications’s plugins. Some of the issues that need to be taken into consideration:

* Plugin dependencies

} ... } Unless you configure things differently, all log output will be written to System.err. Therefore, 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...

    /**
     * Sets up the class realm for the specified plugin. Both the class realm and the plugin artifacts that constitute
     * it will be stored in the plugin descriptor.
     *
     * @param pluginDescriptor The plugin descriptor in which to save the class realm and the plugin artifacts, must not
     *            be {@code null}.

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

import org.apache.maven.lifecycle.LifecycleExecutionException;

/**
 * Provides context for mojo execution. Invocation of {@link #run(MojoExecution)} will result in actual execution
 */
public interface MojoExecutionRunner {
    /**
     * Runs mojo execution
     *
     * @param execution mojo execution
     * @throws LifecycleExecutionException
     */

                        session,
                        pluginArtifact,
                        "Plugin depends on the deprecated Maven 2.x compatibility layer, which will be not supported in Maven 4.x");
            }
        }
    }

     * at the given file or in the given directory.
     */
    @Nullable
    Path locateExistingPom(@Nonnull Path project);

    /**
     * Reads the model from the specified byte stream. The stream will be automatically closed before the method
     * returns.
     *
     * @param request The reader request to deserialize the model, must not be {@code null}.
     * @return The deserialized model, never {@code null}.

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

import org.apache.maven.execution.MavenSession;

/**
 * Allows core extensions to participate in Maven build session lifecycle.
 *
 * All callback methods (will) follow beforeXXX/afterXXX naming pattern to
 * indicate at what lifecycle point it is being called.
 *
 * @see <a href="https://maven.apache.org/examples/maven-3-lifecycle-extensions.html">example</a>

        } catch (ResourceDoesNotExistException e) {
            getLogger()
                    .info(metadata + " could not be found on repository: " + remoteRepository.getId()
                            + ", so will be created");

            // delete the local copy so the old details aren't used.
            if (file.exists()) {
                if (!file.delete()) {