The simpler the problem solved by the tool, the better performance it will get. And most of the benchmarks don't test the additional features provided by the tool.

The hierarchy is like:

* **Uvicorn**: an ASGI server
    * **Starlette**: (uses Uvicorn) a web microframework

            Map<Path, Set<String>> pluginsNeedingManagement =
                    analyzePluginsUsingEffectiveModels(context, pomMap, tempDir);

            // Phase 3: Add plugin management to the last local parent in hierarchy
            for (Map.Entry<Path, Document> entry : pomMap.entrySet()) {
                Path pomPath = entry.getKey();
                Document pomDocument = entry.getValue();
                processedPoms.add(pomPath);

## Project structure

Mostly a standard Maven project structure. The entry point `settings.kts` defines the TeamCity project.

There are 3 subprojects in the TeamCity project hierarchy: `Check` for Gradle builds, `Promotion` for releasing Gradle versions, `Util` for miscellaneous utilities.

## Develop and verify

 * with {@link #where} and types are resolved using {@link #resolveType}.
 *
 * <p>Note that usually type mappings are already implied by the static type hierarchy (for example,
 * the {@code E} type variable declared by class {@code List} naturally maps to {@code String} in
 * the context of {@code class MyStringList implements List<String>}). In such case, prefer to use

     */
    @Nonnull
    List<Profile> getActivePomProfiles();

    /**
     * Gets the profiles that were active during model building for a specific model in the hierarchy.
     * This allows tracking which profiles came from which model (parent vs child).
     *
     * @param modelId The identifier of the model (groupId:artifactId:version) or empty string for the super POM.

     */
    @Nonnull
    S getSession();

    /**
     * Returns the trace information associated with this request, if any.
     * The trace provides context about the request's position in the operation
     * hierarchy and can carry additional diagnostic information.
     *
     * @return the request trace, or {@code null} if no trace information is available
     */
    @Nullable
    RequestTrace getTrace();

    /**

            method.setAccessible(true);
            assertEquals(443, method.invoke(testHandler));
        }

        @Test
        @DisplayName("Should maintain inheritance hierarchy")
        void testInheritanceHierarchy() {
            // When
            Class<?> superclass = Handler.class.getSuperclass();

            // Then

# Build state model

The Gradle daemon tracks state for various elements. These are arranged in a hierarchy:

```mermaid
  graph TD

  process["build process"]
  
  session["build session"]
  process --> session
  
  build_tree["build tree"]
  session --> build_tree
  
  build1["root build"]
  build_tree --> build1
  
  project1["root project"]
  build1 --> project1
  
  project2["project"]
  build1 --> project2

    @Mock
    SmbResourceLocator other;

    @Mock
    DfsReferralData referral;

    // Reflection-based API checks ensure the interface contract is as expected
    @Test
    @DisplayName("Type hierarchy and method signatures are correct")
    void typeAndSignatures() throws Exception {
        Class<?> clazz = SmbResourceLocatorInternal.class;

        // Assert it's an interface and extends the right superinterface

#### Figure 2 - KMS key hierarchy

```
                                                          CMK (master key)
                                                           |