NEXT FRAMES NO FRAMES All Classes org/hamcrest/class-use/Condition.Step.html Overview Package Class Use Tree Deprecated Index Help PREV NEXT FRAMES NO FRAMES All Classes Uses of Interface org.hamcrest.Condition.Step Packages that use Condition.Step org.hamcrest The stable API defining Matcher and its associated interfaces and classes. Uses of Condition.Step in org.hamcrest Methods in org.hamcrest with parameters of type Condition.Step abstract <U> Condition<U> Condition.and(Condition.Step<? super T,U>...

Description); public boolean matching(Matcher, String); public Condition and(Condition$Step); } org/hamcrest/Condition$NotMatched.class package org.hamcrest; final synchronized class Condition$NotMatched extends Condition { private void Condition$NotMatched(); public boolean matching(Matcher, String); public Condition and(Condition$Step); } org/hamcrest/Condition$Step.class package org.hamcrest; public abstract interface Condition$Step { public abstract Condition apply(Object, Description); } org/hamcrest/Condition.class...

        // to specify the absolute path to these files in a customized components.xml
        // file. Ideally, we'd do full pattern-evaluation against the sysprops, but this
        // is a first step. There are several replacements below, in order to normalize
        // the path character before we operate on the string as a regex input, and
        // in order to avoid surprises with the File construction...

    /**
     * Updates the context class loader such that the container will search the project realm when the model builder
     * injects the lifecycle bindings from the packaging in the next step. The context class loader is to be reset by
     * the project builder when the project is fully assembled.
     *
     * @param project The project whose class realm should be selected, must not be {@code null}.
     */

    /**
     * Returns project's all artifacts as immutable collection. The list contains all artifacts, even the attached ones,
     * if any. Hence, the list returned by this method depends on which lifecycle step of the build was it invoked.
     * The head of returned list is result of {@link Project#getArtifacts()} method, so same applies here: the list can have

          <!-- This is a required attribute and is intentionally left empty -->
          <models />
        </configuration>
        <executions>
          <execution>
            <!-- This step is required to generate xdoc, and does not generate java code -->
            <id>modello-site-doc</id>
            <goals>
              <goal>xdoc</goal>
            </goals>
            <phase>pre-site</phase>

messages to be logged (if the corresponding detail level is enabled) by calling appropriate methods (trace(), debug(), info(), warn(), error, and fatal()). For convenience, LogFactory also offers a static method getLog() that combines the typical two-step pattern: Log log = LogFactory.getFactory().getInstance(Foo.class); into a single method call: Log log = LogFactory.getLog(Foo.class); For example, you might use the following technique to initialize and use a Log instance in an application component:...

    } else {
        currentBuild.result = "FAILURE"
    }
    throw e
} catch (hudson.AbortException e) {
    echo "[FAILURE-003] AbortException ${e}"
    // this ambiguous condition means during a shell step, user probably aborted
    if (e.getMessage().contains('script returned exit code 143')) {
        currentBuild.result = "ABORTED"
    } else {
        currentBuild.result = "FAILURE"
    }
    throw e

        }

        return delegate.calculateLifecycleMappings(session, project, lifecycle, lifecyclePhase);
    }

    /**
     * Post-processes the effective configuration for the specified mojo execution. This step discards all parameters
     * from the configuration that are not applicable to the mojo and injects the default values for any missing
     * parameters.
     *

Cause messages to be logged (if the corresponding detail level is enabled) by calling appropriate methods (debug(), info(), warn(), error, and 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...