h3. Creation of an isolated classloader

        System.setProperties(originalSystemProperties);
        resetHandlerState();
    }

    /**
     * Resets the static state of the Handler class using reflection.
     * This is crucial for ensuring that tests are isolated from each other.
     */
    private void resetHandlerState() throws Exception {
        // Reset the static factory field
        Field factoryField = Handler.class.getDeclaredField("factory");

  earmarked as remote should be accessed, regardless of whether it is actually
  a physically local resource.

  NOTE: One side effect of this design change is that all offline-mode code can
  be isolated to maven-core, maven-plugin-descriptor, and [possibly]
  maven-artifact. Usage of maven-wagon will be determined by an offline-aware
  manager.

* Assumptions: What is Offline?

/// info | Very Technical Details

**Note**: this is a very technical detail that you probably can **just skip**.

---

The `APIRouter`s are not "mounted", they are not isolated from the rest of the application.

This is because we want to include their *path operations* in the OpenAPI schema and the user interfaces.

</details>

## What is a Container { #what-is-a-container }

Containers (mainly Linux containers) are a very **lightweight** way to package applications including all their dependencies and necessary files while keeping them isolated from other containers (other applications or components) in the same system.

    expectedClosure.putEdge(N1, N3);
    expectedClosure.putEdge(N2, N2);
    expectedClosure.putEdge(N2, N3);
    expectedClosure.putEdge(N3, N3);
    expectedClosure.addNode(N4); // N4 is isolated => no incident edges in this transitive closure

    assertThat(
      transitiveClosure(undirectedGraph, ADD_SELF_LOOPS_FOR_CYCLES)).isEqualTo(expectedClosure);
  }

  @Test