// Test parent of root - currently throws NPE due to bug in SmbFile.getParent()
            // when authority is null. This is a known issue in the legacy implementation.
            // For now, we expect the NPE to maintain backward compatibility
            assertThrows(NullPointerException.class, () -> new SmbFile("smb1://").getParent());
        }

        @Test
        public void testGetPath() throws MalformedURLException {

 maven.multiproject.includes property.
 2. it works without problems only for projects with relative paths, e.g., from
 one CVS repository.. for projects from multiple SCM repositories it's harder
 to maintain the same relative links on all developer computers.
 not sure the unified source directory structure addresses this issue.

 Properties

 maven.user.config.dir (system,default=${user.home}/.m2)

 *   <li>Handle source roots and resources</li>
 *   <li>Access and modify project properties</li>
 *   <li>Manage repository configurations</li>
 *   <li>Handle project forking states</li>
 * </ul>
 *
 * The service maintains the mutable state of projects as they progress through
 * their build lifecycle, ensuring thread-safety and proper state management.
 * All implementations must be thread-safe as they may be accessed concurrently

 * </ul>
 *
 * <h3>Format Preservation</h3>
 * <ul>
 *   <li><strong>Whitespace Preservation</strong>: Maintains original formatting when removing elements</li>
 *   <li><strong>Comment Preservation</strong>: Preserves XML comments and processing instructions</li>

 * under the License.
 */

/**
 * <h2>Maven Core API</h2>
 *
 * <h3>Session</h3>
 *
 * <p>The {@link org.apache.maven.api.Session} interface is the main entry point for Maven operations.
 * It maintains the state of a Maven execution and provides access to all core services and components.
 * Sessions are thread-safe and can be obtained in session-scoped components using the

7. **Submit** a Pull Request with detailed description

### Code Standards
- Follow the project's Eclipse formatter configuration
- Add Apache License 2.0 headers to new files: `mvn license:format`
- Maintain comprehensive JavaDoc documentation
- Write thorough unit tests with good coverage
- Follow existing naming conventions and patterns

## 📄 License

        NtTransNotifyChange notify3 = new NtTransNotifyChange(mockConfig, 0x3333, FILE_NOTIFY_CHANGE_ATTRIBUTES, false);

        // Verify each instance maintains its own state
        byte[] dst1 = new byte[8];
        byte[] dst2 = new byte[8];
        byte[] dst3 = new byte[8];

        notify1.writeSetupWireFormat(dst1, 0);
        notify2.writeSetupWireFormat(dst2, 0);

        NtTransQuerySecurityDesc desc3 = new NtTransQuerySecurityDesc(mockConfig, 0x3333, DACL_SECURITY_INFORMATION);

        // Verify each instance maintains its own state
        assertEquals(0x1111, desc1.fid);
        assertEquals(OWNER_SECURITY_INFORMATION, desc1.securityInformation);

        assertEquals(0x2222, desc2.fid);

        @DisplayName("Should never return null DfsResponse")
        void testGetDfsResponseNeverNull() {
            assertNotNull(response.getDfsResponse());
        }

        @Test
        @DisplayName("Should maintain DfsResponse after reading data")
        void testGetDfsResponseAfterReadingData() {
            byte[] buffer = createValidDfsReferralBuffer();
            DfsReferralResponseBuffer originalBuffer = response.getDfsResponse();

        assertNull(emptyIterator.next(), "Iterator should still return null after multiple removes");
    }

    @Test
    @DisplayName("EmptyIterator should maintain state after all operations")
    void testStateConsistencyAfterOperations() {
        // When - perform various operations
        assertFalse(emptyIterator.hasNext(), "Initial hasNext check");