/**
     * <p>
     * PluginId =&gt; ExtensionRealmCache.CacheRecord map MavenProject context value key. The map is used to ensure the
     * same class realm is used to load build extensions and load mojos for extensions=true plugins.
     * </p>
     * <strong>Note:</strong> This is part of internal implementation and may be changed or removed without notice
     *
     * @since 3.3.0
     */

org.codehaus.plexus.classworlds.launcher; public synchronized class Configurator { public static final String MAIN_PREFIX = main is; public static final String SET_PREFIX = set; public static final String IMPORT_PREFIX = import; public static final String LOAD_PREFIX = load; public static final String OPTIONALLY_PREFIX = optionally; private Launcher launcher; private org.codehaus.plexus.classworlds.ClassWorld world; private java.util.Map configuredRealms; public void Configurator(Launcher); public void Configu...

org.codehaus.plexus.classworlds.launcher; public synchronized class Configurator { public static final String MAIN_PREFIX = main is; public static final String SET_PREFIX = set; public static final String IMPORT_PREFIX = import; public static final String LOAD_PREFIX = load; public static final String OPTIONALLY_PREFIX = optionally; private Launcher launcher; private org.codehaus.plexus.classworlds.ClassWorld world; private java.util.Map configuredRealms; public void Configurator(Launcher); public void Configu...

     * <p>
     * Using ClassWorld to determine plugin/extensions realm parent classloaders gives m2e and integration test harness
     * flexibility to load multiple version of maven into dedicated classloaders without assuming state of jvm system
     * classloader.
     */
    private static final ClassLoader PARENT_CLASSLOADER = ClassWorld.class.getClassLoader();

                lock = channel.lock();

                if (touchfile.canRead()) {
                    getLogger().debug("Reading resolution-state from: " + touchfile);
                    props.load(Channels.newInputStream(channel));
                }

                props.setProperty(key, Long.toString(System.currentTimeMillis()));

                if (error != null) {

org.codehaus.plexus.classworlds.launcher; public synchronized class Configurator { public static final String MAIN_PREFIX = main is; public static final String SET_PREFIX = set; public static final String IMPORT_PREFIX = import; public static final String LOAD_PREFIX = load; public static final String OPTIONALLY_PREFIX = optionally; private Launcher launcher; private org.codehaus.plexus.classworlds.ClassWorld world; private java.util.Map configuredRealms; public void Configurator(Launcher); public void Configu...

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 wrapper (SimpleLog). Load the class of the specified name from the thread context class loader (if any), or from the class loader that loaded the LogFactory class otherwise. Instantiate an instance of the selected Log implementation class, passing the specified name as the...

  also do this with the lister as well
i'l
// 1 the metadata -> model plugin/mojo descriptor
// 2 tools for doing the mapping
// 3 the component model -> interfaces for the plugin

// The plugin manager should load up a directory structure of plugins.
// - a plugin per directory where the plugin is present with its deps
// - a plugin that has its dependencies packaged up with it

org.codehaus.plexus.classworlds.launcher; public synchronized class Configurator { public static final String MAIN_PREFIX = main is; public static final String SET_PREFIX = set; public static final String IMPORT_PREFIX = import; public static final String LOAD_PREFIX = load; public static final String OPTIONALLY_PREFIX = optionally; private Launcher launcher; private org.codehaus.plexus.classworlds.ClassWorld world; private java.util.Map configuredRealms; public void Configurator(Launcher); public void Configu...

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 that loaded the LogFactory class otherwise. Instantiate an instance of the selected Log implementation class, passing the specified name as the...