The same requirement applies to next/* (described below), which will
become a go1.XX.txt for XX >= 19.

The next/ directory contains the only files intended to be mutated.
Each file in that directory contains a list of features that may be added
to the next release of Go. The files in this directory only affect the
warning output from the go api tool. Each file should be named
nnnnn.txt, after the issue number for the accepted proposal.

        </field>
        <field>
          <name>release</name>
          <version>1.0.0+</version>
          <type>String</type>
          <description>What the last version added to the directory is, for the releases only ("groupId/artifactId" directory only)</description>
        </field>

  <name>Model inheritance test parent: module directory != artifactId</name>
  <description>
    artifactId == "child-artifact-id"
    but expect path on SCM and site == "child"
    feature: support "project.directory" property, ressembling future model addition of "directory" element along "artifactId"
  </description>

  <!-- 5 inherited urls with ${project.directory} added to parent instead of artifactId -->

}

func TestXLStorageIsDirEmpty(t *testing.T) {
	tmp := t.TempDir()

	// Should give false on non-existent directory.
	dir1 := slashpath.Join(tmp, "non-existent-directory")
	if isDirEmpty(dir1, true) {
		t.Error("expected false for non-existent directory, got true")
	}

	// Should give false for not-a-directory.
	dir2 := slashpath.Join(tmp, "file")
	err := os.WriteFile(dir2, []byte("hello"), 0o777)
	if err != nil {

            or module-path resources such as properties files or scripts associated with a project.
            This directory is meant to be different from the main source directory,
            in that its contents will be copied to the output directory in most cases
            (since scripts are interpreted rather than compiled).

└── DirectoryChangeNotifier.java  - Directory change tracking
```

#### 4.2 Implementation Tasks
- [ ] Extend lease implementation for directories
- [ ] Implement directory metadata caching
- [ ] Add directory change notification integration
- [ ] Create parent-child lease relationships
- [ ] Implement directory lease break handling
- [ ] Add directory enumeration caching

#### 4.3 Integration Points

#*    *##end
#*    *###
#*    *### Classworlds is in boot directory, not in lib
#*    *##if ( $project.artifact.artifactId == "plexus-classworlds" )
#*      *##set ( $directory = 'boot' )
#*    *##end
#*    *###
#*    *### copy license file to lib/$artifactId.license
#*    *##set ( $licFile = $directory + '/' + $project.artifact.artifactId + '.license' )

   * insecure recursive delete to delete files and directories that are <i>outside</i> the directory
   * being deleted. This can happen if, after checking that a file is a directory (and not a
   * symbolic link), that directory is deleted and replaced by a symbolic link to an outside
   * directory before the call that opens the directory to read its entries. File systems that
   * support {@code SecureDirectoryStream} do not have this vulnerability.

    (`tensorflow/tensorflow:devel` and `tensorflow/tensorflow:devel-gpu` are no
    longer supported for development). Use TF SIG Build Dockerfiles in
    development to avoid installing the packages directly on your system (in
    which case remember to change the directory from `/root` to `/tensorflow`
    once you get into the running container so `bazel` can find the `tensorflow`
    workspace).

import jcifs.internal.smb1.ServerMessageBlock;

/**
 * SMB1 Delete Directory request message.
 *
 * This command is used to delete a directory on the server.
 * The directory must be empty before it can be deleted.
 */
public class SmbComDeleteDirectory extends ServerMessageBlock {

    /**
     * Creates a new SMB1 delete directory request.
     *
     * @param config the CIFS configuration