// Verify the exception message indicates name resolution failure
        assertTrue(exception.getMessage().contains("NONEXISTENT") || exception.getMessage().contains("unknown")
                || exception.getMessage().contains("not found"), "Exception message should indicate name resolution failure");
    }

    @Test

     *       </ul>
     *       The actual resolution is performed by {@link #targetPath(Project)}.</li>
     *   <li><strong>Absolute Path</strong> (e.g., {@code Path.of("/tmp/custom")}) - The path is used as-is
     *       without any resolution. Files will be copied to this exact location.</li>
     * </ul>
     * <p>

  "Import-Package: " +
    "com.oracle.svm.core.annotate;resolution:=optional," +
    "com.oracle.svm.core.configure;resolution:=optional," +
    "dalvik.system;resolution:=optional," +
    "org.conscrypt;resolution:=optional," +
    "org.bouncycastle.*;resolution:=optional," +
    "org.openjsse.*;resolution:=optional," +
    "org.graalvm.nativeimage;resolution:=optional," +
    "org.graalvm.nativeimage.hosted;resolution:=optional," +

     *
     * @param coordinates coordinates of the artifact to resolve
     * @return requested artifact together with the path to its file
     * @throws org.apache.maven.api.services.ArtifactResolverException if the artifact resolution failed
     *
     * @see org.apache.maven.api.services.ArtifactResolver#resolve(Session, Collection)
     */
    @Nonnull
    DownloadedArtifact resolveArtifact(@Nonnull ArtifactCoordinates coordinates);

            </Export-Package>
            <Import-Package>
              com.google.common.util.concurrent.internal,
              org.jspecify.annotations;resolution:=optional,
              javax.crypto.*;resolution:=optional,
              sun.misc.*;resolution:=optional
            </Import-Package>
            <Bundle-DocURL>https://github.com/google/guava/</Bundle-DocURL>
          </instructions>
        </configuration>

repository. During development in an IDE we would need layered resolution approach that would allow resolution from the workspace, then the local Maven repository and then from any number of remote Maven repositories. During development from the command line we would need a layered resolution approach that would allow resolution from the local Maven repository and then from any number of remote Maven repositories. In production the resolution for the dependencies could also be layered but would depend...

          <description>The type of dependency.</description>
        </field>
      </fields>
    </class>

    <class xdoc.anchorName="resolution">
      <name>Resolution</name>
      <version>2.0.0+</version>
      <description>Dependency collection or resolution injection.</description>
      <fields>
        <field>
          <name>field</name>
          <required>false</required>

import jcifs.smb1.Config;
import jcifs.smb1.UniAddress;
import jcifs.smb1.util.LogStream;

/**
 * Implements DFS (Distributed File System) referral caching and resolution.
 * This class manages DFS referral cache and provides DFS path resolution functionality.
 */
public class Dfs {

    /**
     * Default constructor for Dfs.
     * Initializes the DFS referral system.
     */
    public Dfs() {

 * this class to use jCIFS properly. Name resolusion is
 * handled internally to the <code>jcifs.smb1.smb1</code> package.
 * <p>
 * This class is a wrapper for both {@link jcifs.smb1.netbios.NbtAddress}
 * and {@link java.net.InetAddress}. The name resolution mechanisms
 * used will systematically query all available configured resolution
 * services including WINS, broadcasts, DNS, and LMHOSTS. See

        }
    }

    /**
     * Get members of the group represented by this SID, if it is one.
     *
     * @param authorityServerName the server to use for SID resolution
     * @param tc the CIFS context to use
     * @param flags resolution flags
     * @return the members of the group
     * @throws IOException if there is an error retrieving group members
     */