Use this directory to add third party extensions to Maven Core. These extensions can either extend or override

     * Note: Current implementation throws NullPointerException for null strings.
     */
    @Test
    void testCheck_withNullStringAndZeroPointer() {
        // A zero pointer indicates a null string
        PacUnicodeString pacString = new PacUnicodeString((short) 0, (short) 0, 0);
        String testString = null;

        // Current implementation throws NullPointerException when string is null

        block.uid = 0x1234;
        block.useUnicode = true;

        byte[] buf = new byte[256];
        int n = block.writeAndXWireFormat(buf, 0);

        assertTrue(n > 0);
        // Note: In actual implementation, uid is NOT propagated for non-AndX SMBs
        // uid is only set for AndXServerMessageBlock instances (line 167 in AndXServerMessageBlock.java)
        // Only useUnicode is set before the instanceof check (line 149)

import java.util.concurrent.ExecutionException;

/**
 * This class provides a skeletal implementation of the {@code Cache} interface to minimize the
 * effort required to implement this interface.
 *
 * <p>To implement a cache, the programmer needs only to extend this class and provide an
 * implementation for the {@link #put} and {@link #getIfPresent} methods. {@link #getAllPresent} is

        // Note: Standard Iterator would throw NoSuchElementException, but this implementation returns null
        // This is a design choice for this specific implementation
        assertNull(emptyIterator.next(), "This implementation returns null instead of throwing");

        // Verify remove can be called (even though no-op)

        verify(request, times(1)).size();
        verify(request, times(1)).getOverrideTimeout();
    }

    @Test
    @DisplayName("Test Request with concrete implementation")
    void testConcreteImplementation() {
        // Create a concrete implementation for testing
        TestRequest testRequest = new TestRequest();

        // Test initResponse

 * the backing object, but relies on {@code Object}'s implementation. This is necessary to preserve
 * the symmetry of {@code equals}. Custom definitions of equality are usually based on an interface,
 * such as {@code Set} or {@code List}, so that the implementation of {@code equals} can cast the
 * object being tested for equality to the custom interface. {@code ForwardingObject} implements no

        assertEquals(0, pipe.maxDataCount);

        // Max setup count should be 0
        assertEquals(0, pipe.maxSetupCount);

        // Setup count should be 2 (as per actual implementation)
        assertEquals(2, pipe.setupCount);
    }

    @Test
    public void testWriteSetupWireFormat() {
        // Test the writeSetupWireFormat method

import java.util.Iterator;
import org.jspecify.annotations.NullMarked;
import org.jspecify.annotations.Nullable;

/**
 * A utility for testing an Iterator implementation by comparing its behavior to that of a "known
 * good" reference implementation. In order to accomplish this, it's important to test a great
 * variety of sequences of the {@link Iterator#next}, {@link Iterator#hasNext} and {@link

 * backing store (e.g. file system, database, memory).
 * <p>
 * This is mainly used to parse files into objects such as Maven projects,
 * models, settings, or toolchains. The source implementation handles
 * all the details of accessing the underlying content while providing
 * a uniform API to consumers.
 * <p>
 * Sources can represent:
 * <ul>
 *   <li>Local filesystem files</li>