*/
    @Nonnull
    String getLocation();

    /**
     * Resolves a new source relative to this one.
     * <p>
     * The resolution strategy depends on the source type:
     * <ul>
     *   <li>File sources resolve against their parent directory</li>
     *   <li>URL sources resolve against their base URL</li>
     *   <li>Other sources may not support resolution and return null</li>
     * </ul>

    <configuration>
      <![CDATA[
<dependencies>
  ...
</dependencies>
    ]]></configuration>
    <description>
      <![CDATA[
      This is a set of Artifact instances resolved from the set of dependencies for
      the current project.

      NOTE: This will likely contain much more than the direct dependencies of the
      current POM, since Maven uses transitive, or chained, dependency resolution.

     * </p>
     * <p>
     * This method is the foundation for {@link SourceRoot#targetPath(Project)} path resolution.
     * When a {@link SourceRoot} has a relative {@code targetPath}, it is resolved against the
     * output directory returned by this method for the source root's scope. This ensures that:
     * </p>
     * <ul>

    }

    /**
     * Registers internal distribution resolutions.
     * <p>
     * Elasticsearch distributions are resolved as project dependencies either representing
     * the current version pointing to a project either under `:distribution:archives` or :distribution:packages`.
     * <p>
     * BWC versions are resolved as project to projects under `:distribution:bwc`.
     */

    "groups" : [ {
      "testProject" : "excludeRuleMergingBuild",
      "coverage" : {
        "per_commit" : [ "linux" ]
      }
    } ]
  }, {
    "testId" : "org.gradle.performance.regression.corefeature.ParallelDownloadsPerformanceTest.resolves dependencies from external repository",
    "groups" : [ {

}, {
  "scenario" : "org.gradle.performance.regression.corefeature.LargeDependencyGraphPerformanceTest.resolve large dependency graph from file repo",
  "durations" : [ {
    "testProject" : "excludeRuleMergingBuild",
    "linux" : 465
  } ]
}, {
  "scenario" : "org.gradle.performance.regression.corefeature.ParallelDownloadsPerformanceTest.resolves dependencies from external repository",
  "durations" : [ {
    "testProject" : "springBootApp",

 * {@code List<}{@link org.apache.maven.api.Node Node}{@code >},
 * and {@code pathScope != ""}, the dependencies will be <i>flattened</i>.
 * Else the dependencies will be <i>resolved</i> and {@code pathScope} must be non empty,
 * and the field type can be {@link org.apache.maven.api.Node Node},
 * {@code List<}{@link org.apache.maven.api.Node Node}{@code >},

             *
             * In the case of a worktree, we read the gitdir from the plain text .git file. This resolves to a directory from which we read
             * the HEAD file and resolve commondir to the plain git repository.
             */
            final Path dotGit = rootDir.toPath().resolve(".git");
            final String revision;

     * is queried frequently and exceptions would be rather costly to
     * throw on a regular basis here.
     *
     * @param host the hostname to resolve
     * @return the resolved NbtAddress or null if not found
     */

    public synchronized static NbtAddress getByName(final String host) {
        return getByName(new Name(host, 0x20, null));
    }

This artifact can be resolved by the consumer project as shown in the example below:

```
dependencies {
  //add the test fixtures of `:providing-project` to testImplementation configuration.