want to analyze the set of transitive dependencies, in particular during early lifecycle phases where
            full dependency resolution might fail due to projects which haven't been built yet.
          </description>
        </field>
        <field>
          <name>dependencyCollection</name>
          <version>2.0.0+</version>

                                artifact.setDependencyTrail(node.getDependencyTrail());

                                set.add(node);

                                // This is required right now.
                                result.addArtifact(artifact);
                            }
                        }
                    } catch (OverConstrainedVersionException e) {

    }

    private File getFile(String pathPattern, String basedirSysProp, String altLocationSysProp) {
        // -------------------------------------------------------------------------------------
        // Alright, here's the justification for all the regexp wizardry below...
        //
        // Continuum and other server-like apps may need to locate the user-level and

*/ body { background-color: #FFFFFF; color:#000000 } /* Headings */ h1 { font-size: 145% } /* Table colors */ .TableHeadingColor { background: #CCCCFF; color:#000000 } /* Dark mauve */ .TableSubHeadingColor { background: #EEEEFF; color:#000000 } /* Light mauve */ .TableRowColor { background: #FFFFFF; color:#000000 } /* White */ /* Font used in left-hand frame lists */ .FrameTitleFont { font-size: 100%; font-family: Helvetica, Arial, sans-serif; color:#000000 } .FrameHeadingFont { font-size: 90%; font-family:...

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

import java.io.File;

/**
 * Postprocesses filesystem paths. For instance, a path translator might want to resolve relative paths given in the
 * bean configuration against some base directory.
 *
 */
public interface BeanConfigurationPathTranslator {

    /**
     * Translates the specified path.
     *

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

/**
 * Defines events that Maven fires during a build. <strong>Warning:</strong> This interface might be extended in future
 * Maven versions to support further events. Hence it is strongly recommended to derive custom listeners from
 * {@link AbstractExecutionListener} in order to avoid interoperability problems.
 *
 */

- check to see if anything is missing

    private boolean isProjectPresent = true;

    // ----------------------------------------------------------------------------
    // We need to allow per execution user and global settings as the embedder
    // might be running in a mode where it's executing many threads with totally
    // different settings.
    // ----------------------------------------------------------------------------

    private File userSettingsFile;

fatal()). For convenience, LogFactory also offers a static method getLog() that combines the typical two-step pattern: Log log = LogFactory.getFactory().getInstance("Foo"); into a single method call: Log log = LogFactory.getLog("Foo"); For example, you might use the following technique to initialize and use a Log instance in an application component: import org.apache.commons.logging.Log; import org.apache.commons.logging.LogFactory; public class MyComponent { protected static Log log = LogFactory.get...

        <field xdoc.separator="blank">
          <name>proxies</name>
          <version>1.0.0+</version>
          <description>
            Configuration for different proxy profiles. Multiple proxy profiles
            might come in handy for anyone working from a notebook or other
            mobile platform, to enable easy switching of entire proxy
            configurations by simply specifying the profile id, again either from