* Creates an empty request.
     */
    public DefaultPluginPrefixRequest() {}

    /**
     * Creates a request for the specified plugin prefix and build session. The provided build session will be used to
     * configure repository settings. If the session has a current project, its plugin repositories and model will be
     * used as well.
     *
     * @param prefix The plugin prefix to resolve, must not be {@code null}.

node(jenkinsEnv.nodeSelection(osNode)) {
    dir('build') {
        stage('Checkout') {
            checkout scm
        }

        def WORK_DIR=pwd()
        def MAVEN_GOAL='verify'

        stage('Configure deploy') {
           if (env.BRANCH_NAME in ['master', 'maven-3.8.x', 'maven-3.9.x']){
               MAVEN_GOAL='deploy'
           }
        }

        stage('Build / Unit Test') {

            while (firstRun || retry) {
                ChecksumObserver md5ChecksumObserver = null;
                ChecksumObserver sha1ChecksumObserver = null;
                try {
                    // TODO configure on repository
                    int i = 0;

                    md5ChecksumObserver = addChecksumObserver(wagon, CHECKSUM_ALGORITHMS[i++]);

log.debug("About to do something to object " + name); } name.bar(); } catch (IllegalStateExceptio e) { log.error("Something bad happened to " + name, e); } ... } 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...

Plexus component. Typically this is done within Plexus with the configuration supplied with component configuration, but in Maven we take configuration values from the POM. So we have to use the ComponentConfigurator outside of Plexus in order to configure the Maven Mojo which is just a Plexus component. We can use the information from the MojoDescriptor along with the merged configuration information that is now present in the POM to create the complete PlexusConfiguration used to populate values...

getActiveLoggerCount(); static void <clinit>(); } org/codehaus/plexus/personality/plexus/lifecycle/phase/Configurable.class package org.codehaus.plexus.personality.plexus.lifecycle.phase; public abstract interface Configurable { public abstract void configure(org.codehaus.plexus.configuration.PlexusConfiguration) throws org.codehaus.plexus.configuration.PlexusConfigurationE; } org/codehaus/plexus/personality/plexus/lifecycle/phase/Contextualizable.class package org.codehaus.plexus.personality.plexus.lifecycle.phase;...

or.class package org.codehaus.classworlds; public synchronized class Configurator { private ConfiguratorAdapter config; public void Configurator(Launcher); public void Configurator(ClassWorld); public void setClassWorld(ClassWorld); public void configure(java.io.InputStream) throws java.io.IOException, java.net.MalformedURLExceptio, ConfigurationExcepti, DuplicateRealmExcept, NoSuchRealmException; protected void associateRealms(); protected void loadGlob(String, ClassRealm) throws java.net.MalformedURLExceptio,...

- how to deal with resolution from different places like local/remote/workspace
- how to incorporate the metadata processor to start with
- create a hook to programmatically configure the test
- create a plugin processor
- directory
- jar
- hooks for loading

- I could make an annotation that marked another class as its plugin discoverer, I could just add it to

   | your Tomcat instance is installed, you can provide a variable here such that the variable is
   | dereferenced during the build process to configure the cactus plugin.
   |
   | As noted above, profiles can be activated in a variety of ways. One way - the activeProfiles
   | section of this document (settings.xml) - will be discussed later. Another way essentially

log.debug("About to do something to object " + name); } name.bar(); } catch (IllegalStateExceptio e) { log.error("Something bad happened to " + name, e); } ... } 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...