* This is usually incremented in conjunction with {@link #missCount}, though {@code missCount} is
   * also incremented when an exception is encountered during cache loading (see {@link
   * #loadExceptionCount}). Multiple concurrent misses for the same key will result in a single load
   * operation. This may be incremented not in conjunction with {@code missCount} if the load occurs

   * This is usually incremented in conjunction with {@link #missCount}, though {@code missCount} is
   * also incremented when an exception is encountered during cache loading (see {@link
   * #loadExceptionCount}). Multiple concurrent misses for the same key will result in a single load
   * operation. This may be incremented not in conjunction with {@code missCount} if the load occurs

import java.util.Iterator;
import org.jspecify.annotations.Nullable;

/**
 * An iterator that does not support {@link #remove}.
 *
 * <p>{@code UnmodifiableIterator} is used primarily in conjunction with implementations of {@link
 * ImmutableCollection}, such as {@link ImmutableList}. You can, however, convert an existing
 * iterator to an {@code UnmodifiableIterator} using {@link Iterators#unmodifiableIterator}.
 *

 *   <li>Maintaining consistency in artifact storage patterns</li>
 * </ul>
 *
 * <p>This interface is part of Maven's repository management system and works in
 * conjunction with {@link RemoteRepository} and {@link LocalRepository} to provide
 * a complete artifact resolution and storage solution.
 *
 * @since 4.0.0
 * @see LocalRepository
 * @see RemoteRepository
 * @see Artifact
 */

import static java.lang.annotation.RetentionPolicy.RUNTIME;

/**
 * Provides a unique identifier for dependencies when multiple implementations
 * of the same type are available.
 * <p>
 * This annotation can be used in conjunction with {@link Inject} to specify
 * which implementation should be injected when multiple candidates exist.
 * The value represents a unique identifier for the dependency.
 * <p>
 * Example usage:
 * <pre>

 * hashes via NTLM SSP with MSIE. It might also be used directly by servlet
 * containers to incorporate similar functionality.
 * <p>
 * How NTLMSSP is used in conjunction with HTTP and MSIE clients is
 * described in an <A HREF="http://www.innovation.ch/java/ntlm.html">NTLM
 * Authentication Scheme for HTTP</A>.
 * <p>
 * Also, read <a

        if (settings.get(USER_DICT_PATH_OPTION) != null && settings.get(USER_DICT_RULES_OPTION) != null) {
            throw new IllegalArgumentException(
                    "It is not allowed to use [" + USER_DICT_PATH_OPTION + "] in conjunction" + " with [" + USER_DICT_RULES_OPTION + "]");
        }
        try {
            Set<String> dup = new HashSet<>();
            List<String> ruleList =

     */
    @Size(max = 1000)
    public String ldapAdminSecurityPrincipal;

    /**
     * LDAP admin security credentials (password) for administrative operations.
     * Used in conjunction with the admin security principal.
     */
    @Size(max = 1000)
    public String ldapAdminSecurityCredentials;

    /**
     * LDAP base DN (Distinguished Name) for user searches.

 * hashes via NTLM SSP with MSIE. It might also be used directly by servlet
 * containers to incorporate similar functionality.
 * <p>
 * How NTLMSSP is used in conjunction with HTTP and MSIE clients is
 * described in an <A HREF="http://www.innovation.ch/java/ntlm.html">NTLM
 * Authentication Scheme for HTTP</A>.  <p> Also, read <a

  /**
   * Returns an object that holds a stack trace created at the moment this method is executed. This
   * should be used specifically for [java.io.Closeable] objects and in conjunction with
   * [logCloseableLeak].
   */
  open fun getStackTraceForCloseable(closer: String): Any? =
    when {
      logger.isLoggable(Level.FINE) -> Throwable(closer)

      // These are expensive to allocate.