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
        be available. However, if that file:// url references a
        file-share, as in the case of an NFS or SMB mount, that will

     *
     * @param content
     * @param error
     */
    void debug(CharSequence content, Throwable error);

    /**
     * Send an exception to the user in the <b>debug</b> error level.<br>
     * The stack trace for this exception will be output when this error level is enabled.
     *
     * @param error
     */
    void debug(Throwable error);

    void debug(Supplier<String> content);

 *
 * This is because the ModelProcessor interface extends ModelLocator and ModelReader. If we
 * made this component available under all its interfaces then it could end up being injected
 * into itself leading to a stack overflow.
 *
 * A side effect of using @Typed is that it translates to explicit bindings in the container.
 * So instead of binding the component under a 'wildcard' key it is now bound with an explicit

org/codehaus/plexus/util/xml/SerializerXMLWriter.class package org.codehaus.plexus.util.xml; public synchronized class SerializerXMLWriter implements XMLWriter { private final pull.XmlSerializer serializer; private final String namespace; private final java.util.Stack elements; private java.util.List exceptions; public void SerializerXMLWriter(String, pull.XmlSerializer); public void startElement(String); public void addAttribute(String, String); public void writeText(String); public void writeMarkup(String); public...