OTOH, all offline-mode checks can probably be run from Wagon-based APIs.

** Maven-SCM

  In all but trivial examples, SCM operations cannot complete without
  having access to the versioning server. Therefore, it is assumed that
  any SCM-related activity will be unavailable when m2 is in offline
  mode.

** Maven-Core

    @Test
    void testCompleteModelWithoutParent() throws Exception {
        PomTestWrapper pom = buildPom("complete-model/wo-parent");

        testCompleteModel(pom);
    }

    @Test
    void testCompleteModelWithParent() throws Exception {
        PomTestWrapper pom = buildPom("complete-model/w-parent/sub");

        testCompleteModel(pom);
    }

    }

    /**
     * Gets the identifier of the model from which the problem originated. While the general form of this identifier is
     * <code>groupId:artifactId:version</code> the returned identifier need not be complete. The identifier is derived
     * from the information that is available at the point the problem occurs and as such merely serves as a best effort
     * to provide information to the user to track the problem back to its origin.

            and {@code test-jar}: see <a href="../maven-core/artifact-handlers.html">default
            artifact handlers</a> for a list. New types can be defined by extensions, so this is not a complete list.
            ]]>
          </description>
          <type>String</type>
          <defaultValue>jar</defaultValue>
        </field>
        <field>
          <name>classifier</name>

import static java.lang.annotation.RetentionPolicy.RUNTIME;

/**
 * Indicates that annotated component should be instantiated before session execution starts
 * and discarded after session execution completes.
 *
 * TODO: this is currently not implemented
 *
 * @since 4.0.0
 */
@Scope
@Documented
@Retention(RUNTIME)
@Target({TYPE, METHOD})

import static java.lang.annotation.RetentionPolicy.RUNTIME;

/**
 * Indicates that annotated component should be instantiated before session execution starts
 * and discarded after session execution completes.
 *
 * TODO: this is currently not implemented
 *
 * @since 4.0.0
 */
@Scope
@Documented
@Retention(RUNTIME)
@Target({TYPE, METHOD})

import static java.lang.annotation.RetentionPolicy.RUNTIME;

/**
 * Indicates that annotated component should be instantiated before mojo execution starts and discarded after mojo
 * execution completes.
 *
 * @since 3.1.2
 */
@Target({TYPE})
@Retention(RUNTIME)
@ScopeAnnotation

Quick Build
-------
If you want to bootstrap Maven, you'll need:
- Java 17+
- Maven 3.6.3 or later
- Run Maven, specifying a location into which the completed Maven distro should be installed:
    ```
    mvn -DdistributionTargetDir="$HOME/app/maven/apache-maven-4.0.x-SNAPSHOT" clean package
    ```


[home]: https://maven.apache.org/

    public static final int TRANSFER_INITIATED = 0;

    /**
     * A transfer was started.
     */
    public static final int TRANSFER_STARTED = 1;

    /**
     * A transfer is completed.
     */
    public static final int TRANSFER_COMPLETED = 2;

    /**
     * A transfer is in progress.
     */
    public static final int TRANSFER_PROGRESS = 3;

    /**
     * An error occurred during transfer
     */

import static java.lang.annotation.RetentionPolicy.RUNTIME;

/**
 * Indicates that annotated component should be instantiated before session execution starts
 * and discarded after session execution completes.
 *
 * @since 3.2.0
 */
@Target({TYPE})
@Retention(RUNTIME)
@ScopeAnnotation