import java.io.File;

/**
 * Locates a POM file within a project base directory.
 *
 * @deprecated use {@code org.apache.maven.api.services.ModelBuilder} instead
 */
@Deprecated(since = "4.0.0")
public interface ModelLocator {

    /**
     * Locates the POM file within the specified project directory. In case the given project directory does not exist

        }
        return Optional.empty();
    }

    @Override
    @Nonnull
    public Optional<String> directory() {
        if (commandLine.hasOption(CLIManager.DIRECTORY)) {
            return Optional.of(commandLine.getOptionValue(CLIManager.DIRECTORY));
        }
        return Optional.empty();
    }

    @Override
    @Nonnull
    public Optional<Boolean> infer() {

	// Points to current configuration directory -- deprecated, to be removed in future.
	globalConfigDir = defaultConfigDir
	// Points to current certs directory set by user with --certs-dir
	globalCertsDir = defaultCertsDir
	// Points to relative path to certs directory and is <value-of-certs-dir>/CAs
	globalCertsCADir = defaultCertsCADir
)

// Get - returns current directory.
func (dir *ConfigDir) Get() string {
	return dir.path

type result struct {
	dir     string
	entries []string
}

// Test to read empty directory.
func setupTestReadDirEmpty(t *testing.T) (testResults []result) {
	// Add empty entry slice for this test directory.
	testResults = append(testResults, result{t.TempDir(), []string{}})
	return testResults
}

// Test to read non-empty directory with only files.
func setupTestReadDirFiles(t *testing.T) (testResults []result) {

public interface SourceRoot {
    /**
     * {@return the root directory where the sources are stored}
     * The path is relative to the <abbr>POM</abbr> file.
     *
     * <h4>Default implementation</h4>
     * The default value depends on whether a {@linkplain #module() module name} is specified in this source root:
     * <ul>
     *   <li>
     *     If no module name, then the default directory is

 []

 Depending on what the directory represents ("groupId", "groupId/artifactId" or "groupId/artifactId/version"),
 the Maven Repository Metadata file contains 3 different sets of metadata:

 [[1]] in a "groupId" directory: a "groupId" directory may contain Maven plugins artifacts, which are described in metadata's <<<plugins>>> element,

  <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 -->

## For developers

Release notes should be added to `next` by editing existing files or creating
new files. **Do not add RELNOTE=yes comments in CLs.** Instead, add a file to
the CL (or ask the author to do so).

At the end of the development cycle, the files will be merged by being
concatenated in sorted order by pathname. Files in the directory matching the

     * The path matcher returned by this method expects directory paths.
     * If that matcher returns {@code false}, then the directory will definitively not contain
     * the paths selected by the matcher given in argument to this method.
     * In such case, the whole directory and all its sub-directories can be skipped.

   * 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.