# Testing Dependencies with Overrides

## Overriding dependencies during testing

There are some scenarios where you might want to override a dependency during testing.

You don't want the original dependency to run (nor any of the sub-dependencies it might have).

Directory for files of schema info

Files are auto-generated by DBFlute tasks.

    # /- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    # o documentOutputDirectory: (NotRequired - Default './output/doc')
    #  The output directory mainly for SchemaHtml and DataXlsTemplate.
    #  Basically you don't need this.
    #  It is considered of value that it always exists at same plain.
    #
    #; documentOutputDirectory = ./output/doc
    # - - - - - - - - - -/

    }

    @AfterTemplate
    CharMatcher after() {
      return CharMatcher.ascii();
    }
  }

  class Digit {
    @BeforeTemplate
    CharMatcher before() {
      return CharMatcher.DIGIT;
    }

    @AfterTemplate
    CharMatcher after() {
      return CharMatcher.digit();
    }
  }

  class JavaDigit {
    @BeforeTemplate
    CharMatcher before() {
      return CharMatcher.JAVA_DIGIT;

public final synchronized class CommandLineParser { public static final java.util.regex.Pattern OPTION_NAME_PATTERN; public final java.util.HashMap optionsByString; public boolean allowUnknownOptions; public void CommandLineParser(); static void <clinit>(); public final transient CommandLineOption option(String[]); } org/gradle/cli/ParsedCommandLine.class package org.gradle.cli; public final synchronized class ParsedCommandLine { public final java.util.HashMap optionsByString; public final java.util.HashSet...

              });
    }

    threadPool.shutdown();
    threadPool.awaitTermination(300, SECONDS);

    // Since we're not doing any more cache operations, and the cache only expires/evicts when doing
    // other operations, the cache and the removal queue won't change from this point on.

    // Verify that each received removal notification was valid
    for (RemovalNotification<String, String> notification : removalListener) {

format that Mercury could utilize to resolve and retrieve dependencies. We need to be careful that we are using Mercury during development and production so that we don’t get in the situation where Maven 2.x is resolving differently than Mercury is. We can still leverage POMs during development but we need to make sure Mercury is doing the work.

With respect to development inside an IDE the workspace from which we would like to resolve and retrieve dependencies is a read-only local repository...

    sidecar.istio.io/inject: "false"
  ingress_enabled: false
  image_pull_policy: IfNotPresent
login_token:
  signing_key: CHANGEME00000000
external_services:
  # Kiali will not start up without tracing service. We don't want to require it.
  tracing:

    }

    protected String resolveVersion(Artifact artifact, RepositoryRequest request)
            throws RepositoryMetadataResolutionException {
        RepositoryMetadata metadata;
        // Don't use snapshot metadata for LATEST (which isSnapshot returns true for)
        if (!artifact.isSnapshot() || Artifact.LATEST_VERSION.equals(artifact.getBaseVersion())) {
            metadata = new ArtifactRepositoryMetadata(artifact);

     * TODO(cpovirk): move ForwardingTestCase somewhere common, and use it to
     * test the forwarded methods
     */
  }

  @AndroidIncompatible // Mocking ExecutorService is forbidden there. TODO(b/218700094): Don't mock.
  public void testListeningDecorator_noWrapExecuteTask() {
    ExecutorService delegate = mock(ExecutorService.class);
    ListeningExecutorService service = listeningDecorator(delegate);
    Runnable task =