// that the temporary file is in the same file system as the destination because the
            // File.renameTo operation doesn't really work across file systems.
            // So we will attempt to do a File.renameTo for efficiency and atomicity, if this fails
            // then we will use a brute force copy and delete the temporary file.
            if (!temp.renameTo(destination)) {
                try {

          <type>String</type>
        </field>
        <field>
          <name>interactiveMode</name>
          <version>1.0.0+</version>
          <description>
            Whether Maven should attempt to interact with the user for input.
          </description>
          <type>boolean</type>
          <defaultValue>true</defaultValue>
        </field>
        <field>
          <name>usePluginRegistry</name>

der.class package org.junit.rules; public synchronized class TemporaryFolder extends ExternalResource { private final java.io.File parentFolder; private final boolean assureDeletion; private java.io.File folder; private static final int TEMP_DIR_ATTEMPTS = 10000; private static final String TMP_PREFIX = junit; public void TemporaryFolder(); public void TemporaryFolder(java.io.File); protected void TemporaryFolder(TemporaryFolder$Builder); public static TemporaryFolder$Builder builder(); protected...

 */
public class DependencyResolutionRequiredException extends Exception {
    public DependencyResolutionRequiredException(Artifact artifact) {
        super("Attempted to access the artifact " + artifact + "; which has not yet been resolved");
    }

   | the parameter in question.
   |
   | Default: true
  <interactiveMode>true</interactiveMode>
  -->

  <!-- offline
   | Determines whether maven should attempt to connect to the network when executing a build.
   | This will have an effect on artifact downloads, artifact deployment, and others.
   |
   | Default: false
  <offline>false</offline>
  -->

  <!-- pluginGroups

 * know which version of library the class comes from
 */

This document outlines the concerns of a general plugin manager that would be used in conjunction with any Plexus-based application. The following outlined concerns are an attempt to describe what a plugin manager would need to do for Maven and for Nexus.

h2. Concerns for the plugin manager

h3. Resolving the dependencies of a plugin