<dependency>
      <groupId>org.jline</groupId>
      <artifactId>jline-reader</artifactId>
    </dependency>
    <dependency>
      <groupId>org.jline</groupId>
      <artifactId>jline-terminal-jni</artifactId>
    </dependency>
    <dependency>
      <groupId>org.jline</groupId>
      <artifactId>jline-terminal-ffm</artifactId>
    </dependency>

    <!-- (legacy) DI annotations -->
    <dependency>

# Witness
jcifs.smb.client.useWitness=true
jcifs.smb.client.witnessNotificationTimeout=5000
```

## Risk Assessment

### Technical Risks
1. **RDMA Complexity**: Limited Java RDMA support may require JNI
2. **Multi-Channel Synchronization**: Complex thread synchronization required
3. **Persistent Handle State**: Requires reliable state persistence mechanism
4. **Backward Compatibility**: Must maintain compatibility with SMB2/SMB1

empty such reference is 0, not nil.

These special cases were introduced in Go 1.10. For auto-updating code
from Go 1.9 and earlier, use the cftype or jni rewrites in the Go fix tool:

	go tool fix -r cftype <pkg>
	go tool fix -r jni <pkg>

It will replace nil with 0 in the appropriate places.

The EGLDisplay case was introduced in Go 1.12. Use the egl rewrite
to auto-update code from Go 1.11 and earlier: