However, this does not fully remove the prerequisite, as the Wrapper itself would still need an installed Java runtime to execute.

Gradle needs a solution that covers the use-case of starting the Wrapper itself as well given its importance.

### Running Gradle on multiple Java versions

// Here you should declare versions which should be shared by the different modules of buildSrc itself
val javaParserVersion = "3.18.0"
// Note: this currently still contains 3/4 logic as we will temporarily have Groovy 3 for the build itself until we move to a Gradle built with Groovy 4
// It can be removed or changed to 4/5 logic (if necessary) at that point.

        // Then
        assertNotNull(signingKey, "Should handle empty session key");
        assertEquals(16, signingKey.length, "Should still produce 16-byte key");
    }

    @Test
    @DisplayName("Should handle null preauth integrity for SMB 3.0.0")
    void testDeriveKeys_NullPreauthForSMB300() {
        // Given

        }
    }

    /**
     * Continues an MD4 message digest using the input byte.
     */
    @Override
    public void engineUpdate(final byte b) {
        // compute number of bytes still unhashed; ie. present in buffer
        final int i = (int) (count % BLOCK_LENGTH);
        count++; // update number of bytes
        buffer[i] = b;
        if (i == BLOCK_LENGTH - 1) {
            transform(buffer, 0);

   * next} field is lazily initialized. The type of that field would be {@code @Nullable T}, and the
   * code would be responsible for populating a "real" {@code T} (which might still be the value
   * {@code null}!) before returning it to callers. Depending on how the code is structured, a
   * nullness analysis might not understand that the field has been populated. To avoid that problem

   * next} field is lazily initialized. The type of that field would be {@code @Nullable T}, and the
   * code would be responsible for populating a "real" {@code T} (which might still be the value
   * {@code null}!) before returning it to callers. Depending on how the code is structured, a
   * nullness analysis might not understand that the field has been populated. To avoid that problem

```

////

## Recap { #recap }

Apart from all the fancy words used here, the **Dependency Injection** system is quite simple.

Just functions that look the same as the *path operation functions*.

But still, it is very powerful, and allows you to declare arbitrarily deeply nested dependency "graphs" (trees).

/// tip

All this might not seem as useful with these simple examples.

     */
    SmbPipeResource getPipe(String url, int pipeType) throws CIFSException;

    /**
     * Close all connections and release resources associated with this context
     *
     * @return whether any connection was still in use
     * @throws CIFSException if an error occurs during cleanup
     */
    boolean close() throws CIFSException;

    /**
     * Get the configuration object for this context
     *

        // Assert - verify interaction with dependency
        verify(tree, times(1)).connectLogon(context);
        verify(tree, never()).close();
    }

    @Test
    @DisplayName("connectLogon accepts null context but still invokes")
    void connectLogon_withNull_isInvoked() throws Exception {
        // Act
        tree.connectLogon(null);

        // Assert - even null should be passed through to implementation

  }

  @Override
  public final boolean equals(@Nullable Object obj) {
    if (obj instanceof Subscriber) {
      Subscriber that = (Subscriber) obj;
      // Use == so that different equal instances will still receive events.
      // We only guard against the case that the same object is registered
      // multiple times
      return target == that.target && method.equals(that.method);
    }
    return false;
  }