/**
     * <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
     */

     * <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) {

Offline Mode Design

* UPDATE: 18-April-2005

  We cannot take the approach outlined below of detecting which remote
  repositories are "really" offline, since offline mode is more of a behavior,
  and this will lead to counter-intuitive results. A different feature may exist
  unimplemented, which is to detect when the network is down and provide better
  feedback for that case. However, when offline mode is declared, nothing

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...

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...