* do we need a sort of bus for application data
* do we need a dictionary for our applications like Apple does. We could easily hook into this and this is the model we need to follow. Following the model of apple applications the dictionary is what the REST URI should attach to. Not creating custom logic in the resource code.

        private static final String MAVEN_WRAPPER_PLUGIN_VERSION = "3.2.0";

        @Override
        public String id() {
            return WRAPPER;
        }

        @Override
        public Collection<Phase> phases() {
            return singleton(phase(
                    "wrapper",
                    plugin(

        assertThat(lifecycle.getPhases(), hasSize(4));
    }

    @Test
    void testWrapperLifecycle() {
        final Lifecycle lifecycle = getLifeCycleById("wrapper");
        assertThat(lifecycle.getId(), is("wrapper"));
        assertThat(lifecycle.getPhases(), hasSize(1));
    }

    @Test
    void testCustomLifecycle() throws ComponentLookupException {

                VersionRange.createFromVersion("1.0"),
                "type",
                null,
                "system",
                "compile");

        // this one should never happen in practice...
        Artifact artifact5 = factory.createDependencyArtifact(
                "test-grp", "test-artifact-5", VersionRange.createFromVersion("1.0"), "type", null, "system", "system");

 * under the License.
 */
package org.apache.maven.repository.metadata;

import org.apache.maven.artifact.ArtifactScopeEnum;

/**
 * metadata graph vertice - just a wrapper around artifact's metadata
 *
 */
@Deprecated
public class MetadataGraphVertex implements Comparable<MetadataGraphVertex> {
    ArtifactMetadata md;

    // indications to use these in comparison

            if (longValue > Integer.MAX_VALUE) {
                return null;
            }
            return (int) longValue;
        } catch (NumberFormatException e) {
            // should never happen since checked isDigits(s) before
            return null;
        }
    }

    @Override
    public String toString() {
        return comparable.toString();
    }

to pre-1.0 versions of this API, a system property org.apache.commons.logging.log is also consulted). If the Log4J logging system is available in the application class path, use the corresponding wrapper class (Log4JLogger). If the application is executing on a JDK 1.4 system, use the corresponding wrapper class (Jdk14Logger). Fall back to the default simple logging implementation (SimpleLog). Load the class of the specified name from the thread context class loader (if any), or from the class loader...

java.io.File); public abstract void directoryWalkFinishe(); public abstract void debug(String); } org/codehaus/plexus/util/ExceptionUtils.class package org.codehaus.plexus.util; public synchronized class ExceptionUtils { static final String WRAPPED_MARKER = [wrapped] ; protected static String[] CAUSE_METHOD_NAMES; protected void ExceptionUtils(); public static void addCauseMethodName(String); public static Throwable getCause(Throwable); public static Throwable getCause(Throwable, String[]); public static...

public class MappedCollection<U, V> extends AbstractCollection<U> {
    private final Collection<V> list;
    private final Function<V, U> mapper;

    public MappedCollection(Collection<V> list, Function<V, U> mapper) {
        this.list = list;
        this.mapper = mapper;
    }

    @Override
    public Iterator<U> iterator() {
        Iterator<V> it = list.iterator();
        return new Iterator<U>() {

            // The root locator can be used very early during the setup of Maven,
            // even before the arguments from the command line are parsed.  Any exception
            // that would happen here should cause the build to fail at a later stage
            // (when actually parsing the POM) and will lead to a better exception being
            // displayed to the user, so just bail out and return false.
        }