addFeedback("Failed to extract \'" + expression + "\' from: " + root, e);
            }

            return null;
        }
    }

    /**
     * Wraps another value source and intercepts interpolated expressions, checking for problems.
     *
     */
    static class ProblemDetectingValueSource implements ValueSource {

        private final ValueSource valueSource;

         * the project already contains the plugin executions induced by the project's packaging type. Remember, all
         * phases of interest and only those are in the lifecycle mapping, if a phase has no value in the map, we are
         * not interested in any of the executions bound to it.
         */

        for (Plugin plugin : project.getBuild().getPlugins()) {

* Assumptions: What is Offline?

  For the purposes of determining the areas sensitive to offline status,
  it is definitely useful to define what the offline state really means.

  [[1]] This is obvious, but the network/internet is unavailable.

  [[2]] Localhost (127.0.0.1) may also be unavailable if the whole
        network stack is offline.

  [[3]] "Remote" repositories referenced using the file:// protocol may

school, if any, to sign a "copyright disclaimer" for the program, if
necessary. Here is a sample; alter the names:

    Yoyodyne, Inc., hereby disclaims all copyright interest in the
    program `Gnomovision' (which makes passes at compilers) written by
    James Hacker.

    signature of Ty Coon, 1 April 1989
    Ty Coon, President of Vice

  <description>
    Test that properties which refer to build directories which in turn refer to other build directories are
    properly interpolated.
  </description>

  <properties>
    <!-- These are the properties of interest -->
    <dir0>${project.build.outputDirectory}/dir0</dir0>
    <dir1>${project.build.testSourceDirectory}/dir1</dir1>
    <dir2>${project.reporting.outputDirectory}/dir2</dir2>
  </properties>

  <build>

Frames/No Frames These links show and hide the HTML frames. All pages are available with or without frames. Serialized Form Each serializable or externalizable class has a description of its serialization fields and methods. This information is of interest to re-implementors, not to developers using the API. While there is no link in the navigation bar, you can get to this information by going to any serialized class and clicking "Serialized Form" in the "See also" section of the class description....

         * The result will contain only the paths of types for which the predicate returned {@code true}.
         * It is recommended to apply a filter for retaining only the types of paths of interest,
         * because it can resolve ambiguities when a path could be of many types.
         *
         * @param pathTypeFilter predicate evaluating whether a path type should be included in the result

org.junit.runner.manipulation; final synchronized class Filter$1 extends Filter { void Filter$1(); public boolean shouldRun(org.junit.runner.Description); public String describe(); public void apply(Object) throws NoTestsRemainExcepti; public Filter intersect(Filter); } org/junit/runner/manipulation/Filter$3.class package org.junit.runner.manipulation; synchronized class Filter$3 extends Filter { void Filter$3(Filter, Filter, Filter); public boolean shouldRun(org.junit.runner.Description); public String...