* The packaging type determines the structure of the project's output and how Maven will treat the resulting artifact.</p>
 *
 * <p>Common packaging types include {@code jar}, {@code war}, {@code pom}, {@code maven-plugin}, {@code ear}, and others.
 * These types influence various aspects of the build lifecycle, such as which plugins are executed and how dependencies are managed.</p>
 *

    void testReadBytesWireFormatMaxBufferIndex() throws SMBProtocolDecodingException {
        byte[] buffer = new byte[65536]; // Large buffer
        int bufferIndex = 65534; // Near the end

        // Set structure size to 2
        SMBUtil.writeInt2(2, buffer, bufferIndex);

        int result = response.readBytesWireFormat(buffer, bufferIndex);

        assertEquals(2, result);

        ]]></description>
          <association>
            <type>Repository</type>
            <multiplicity>*</multiplicity>
          </association>
          <comment><![CDATA[ This may be removed or relocated in the near
            future. It is undecided whether plugins really need a remote
            repository set of their own. ]]></comment>
        </field>
      </fields>
    </class>
    <class>

        int result2 = response2.readDataWireFormat(buffer, 20, sourceData.length);
        assertEquals(sourceData.length, result2);

        // Test with offset near end
        byte[] outputBuffer3 = new byte[1024];
        TransCallNamedPipeResponse response3 = new TransCallNamedPipeResponse(mockConfig, outputBuffer3);
        System.arraycopy(sourceData, 0, buffer, 45, sourceData.length);

Then, near the end of the `Dockerfile`, we copy all the code. As this is what **changes most frequently**, we put it near the end, because almost always, anything after this step will not be able to use the cache.

```Dockerfile
COPY ./app /code/app
```

     */

    /**
     * Establishes a connection to the remote endpoint.
     *
     * @throws Exception if the connection fails
     */
    protected abstract void doConnect() throws Exception;

    /* Tear down a connection. If the hard parameter is true, the diconnection
     * procedure should not initiate or wait for any outstanding requests on
     * this transport.
     */

    /**

      fileToClose?.closeQuietly()
    }
  }

  companion object {
    // TODO(jwilson): what to do about timeouts? They could be different and unfortunately when any
    //     timeout is hit we like to tear down the whole stream.

    private const val SOURCE_UPSTREAM = 1
    private const val SOURCE_FILE = 2

    @JvmField val PREFIX_CLEAN = "OkHttp cache v1\n".encodeUtf8()

   * key, the choice of {@link KeyAbsentBehavior} decides which index is returned.
   *
   * <p>This method runs in log(n) time on random-access lists, which offer near-constant-time
   * access to each list element.
   *
   * @param list the list to be searched.
   * @param key the value to be searched for.
   * @param comparator the comparator by which the list is ordered.

            assertTrue(result1 > 0);

            // Test at buffer middle
            int result2 = request.encode(buffer, 128);
            assertTrue(result2 > 0);

            // Test near buffer end (should still fit)
            request.setEncodedSize(16);
            int result3 = request.encode(buffer, 240);
            assertEquals(16, result3);
        }

        @Test

          <association>
            <type>Repository</type>
            <multiplicity>*</multiplicity>
          </association>
          <comment>
            This may be removed or relocated in the near
            future. It is undecided whether plugins really need a remote
            repository set of their own.
          </comment>
        </field>
        <field xdoc.separator="blank">