Donations
---------
Do you like Apache Maven? Then [donate back to the ASF](https://www.apache.org/foundation/contributing.html) to support the development.

Quick Build
-------
If you want to bootstrap Maven, you'll need:
- Java 17+
- Maven 3.9.0 or later
- Run Maven, specifying a location into which the completed Maven distro should be installed:
    ```

        // TODO: Staging directory should be a part of the Javadocs extension
        // TODO: Pull out more of this configuration into the extension if it makes sense
        // TODO: in a typical project, this may need to be the regular javadoc task vs javadocAll

        var groovyPackageListBucket = project.getConfigurations().dependencyScope("groovyPackageListBucket");

 * on [ExchangeCodec], which handles the actual I/O.
 */
class Exchange(
  internal val call: RealCall,
  internal val finder: ExchangeFinder,
  private val codec: ExchangeCodec,
) {
  /** True if the request body need not complete before the response body starts. */
  internal var isDuplex: Boolean = false
    private set

  /** True if there was an exception on the connection to the peer. */
  internal var hasFailure: Boolean = false

  private final Set<Method> suppressedTests = new HashSet<>();

  /**
   * Prevents the given methods from being run as part of the test suite.
   *
   * <p>Note: in principle this should never need to be used, but it might be useful if the
   * semantics of an implementation disagree in unforeseen ways with the semantics expected by a
   * test, or to keep dependent builds clean in spite of an erroneous test.
   */

    } catch (NoSuchMethodException e) {
      throw new AssertionError(e);
    }
  }

  private static @Nullable Field getInheritableThreadLocalsField() {
    if (isAndroid()) {
      /*
       * We need not worry about class unloading under Android. Plus, this approach doesn't always
       * work under Android.
       *
       * (Clearing inheritableThreadLocals could still be useful independent of class unloading, but

        handlers.clear();
    }

    /**
     * Pre-populates the protocol handlers cache with mock handlers for testing.
     * This avoids the need for actual protocol handlers to be available.
     */
    private void setupMockProtocolHandlers() throws Exception {
        Field handlersField = Handler.class.getDeclaredField("PROTOCOL_HANDLERS");

        // Given
        Smb2CloseRequest request = new Smb2CloseRequest(mockConfig, emptyFileId);

        // When
        request.setFileId(testFileId);

        // Then - verify through internal state (would need getter or reflection in real scenario)
        // Since we can't directly verify the internal state, we create a new request to test
        Smb2CloseRequest newRequest = new Smb2CloseRequest(mockConfig, testFileId);

        // Verify time was read correctly (accounting for UTime conversion)
        long readTime = (Long) getFieldValue(response, "lastWriteTime");
        // UTime is seconds since 1970, so we need to compare at second precision
        assertEquals(lastWriteTime / 1000, readTime / 1000);
    }

    @Test
    void testReadParameterWordsWireFormatWithZeroWordCount() {
        // Test reading when wordCount is 0

        v.add(new DERTaggedObject(true, 2, new DERBitString(new byte[] { 0x01 })));

        // Create a custom APPLICATION tagged object that throws IOException when encoding
        // We need to create a proper ASN1TaggedObject with APPLICATION tag class
        // Create a custom base object that throws IOException
        ASN1Encodable badBase = new ASN1Encodable() {
            @Override

From the list of deployment concepts from above, using workers would mainly help with the **replication** part, and a little bit with the **restarts**, but you still need to take care of the others:

* **Security - HTTPS**
* **Running on startup**
* ***Restarts***
* Replication (the number of processes running)
* **Memory**
* **Previous steps before starting**