<description>
            Flags this Mojo as requiring information about the dependencies that would make up the specified class
            path. As the name suggests, this is similar to requiresDependencyResolution and supports the same values.
            The important difference is this will not resolve the files for the dependencies, i.e. the artifacts

    remote-only, and are therefore sensitive to offline mode.

** Maven-Artifact

  This is wholly dependent on Maven-Wagon, above.

  We could possibly use a flag on a particular Wagon to see whether it supports
  offline mode, and then test to see if the file-based basedir for an artifact
  repository works...if it doesn't work, we can mark that repository offline...

    public void validate(Settings settings, boolean isProjectSettings, List<BuilderProblem> problems) {
        if (isProjectSettings) {
            String msgS = "is not supported on project settings.";
            String msgP = "are not supported on project settings.";
            if (settings.getLocalRepository() != null
                    && !settings.getLocalRepository().isEmpty()) {

                // Translate to proper resolver configuration properties as well (as Plexus XML above is Wagon specific
                // only) but support only configuration/httpConfiguration/all, see
                // https://maven.apache.org/guides/mini/guide-http-settings.html
                Map<String, String> headers = null;
                Integer connectTimeout = null;

org/apache/commons/logging/package.html Simple wrapper API around multiple logging APIs. Overview This package provides an API for logging in server-based applications that can be used around a variety of different logging implementations, including prebuilt support for the following: Log4J (version 1.2 or later) from Apache's Jakarta project. Each named Log instance is connected to a corresponding Log4J Logger. JDK Logging API, included in JDK 1.4 or later systems. Each named Log instance is connected to a corresponding...

        } catch (DependencyResolutionException e) {
            result = e.getResult();

            /*
             * MNG-2277, the check below compensates for our bad plugin support where we ended up with aggregator
             * plugins that require dependency resolution although they usually run in phases of the build where project

        }
        sb.append("]");
        return sb.toString();
    }
            ]]>
          </code>
        </codeSegment>
      </codeSegments>
    </class>
    <!-- Profile support -->
    <class>
      <name>Profile</name>
      <version>1.0.0+</version>
      <superClass>IdentifiableBase</superClass>
      <description>

     * Checks whether the layouts configured for a mirror match with the layout of the repository.
     *
     * @param repoLayout The layout of the repository, may be {@code null}.
     * @param mirrorLayout The layouts supported by the mirror, may be {@code null}.
     * @return {@code true} if the layouts associated with the mirror match the layout of the original repository,
     *         {@code false} otherwise.
     */

                    </plugin>
                </plugins>
            </build>
        </profile>
        <profile>
            <id>restrict-doclint</id>
            <!-- doclint is only supported by JDK 8 -->
            <activation>
                <jdk>[1.8,)</jdk>
            </activation>
            <build>
                <plugins>
                    <plugin>

org/apache/commons/logging/package.html Simple wrapper API around multiple logging APIs. Overview This package provides an API for logging in server-based applications that can be used around a variety of different logging implementations, including prebuilt support for the following: Log4J (version 1.2 or later) from Apache's Jakarta project. Each named Log instance is connected to a corresponding Log4J Logger. JDK Logging API, included in JDK 1.4 or later systems. Each named Log instance is connected to a corresponding...