configurations downstream, and GWT uses the runtime configuration for
         its builds. Thus, GWT doesn't get j2objc-annotations transitively, in
         contrast to the other deps of `guava`, which it does get transitively.
         (Arguably we should redeclare *all* the `guava` deps here.) -->
    <dependency>
      <groupId>com.google.j2objc</groupId>
      <artifactId>j2objc-annotations</artifactId>

    go mod vendor
    go test cmd/internal/moddeps

Use caution when passing '-u' to 'go get'. The '-u' flag updates
modules providing all transitively imported packages, not only
the module providing the target package.

Note that 'go mod vendor' only copies packages that are transitively
imported by packages in the current module. If a new package is needed,
it should be imported before running 'go mod vendor'.

        // We do not support running junit from Ant. Don't bundle ant-junit.
        applyRule<DependencyRemovalByNameRule>("org.apache.groovy:groovy-ant", setOf("ant-junit"))

        // GCS transitively depends on commons-logging.
        // Ensure jcl-over-slf4j is pulled in when we use GCS so it can conflict.
        applyRule<DependencyAdditionRule>("com.google.apis:google-api-services-storage", "org.slf4j:jcl-over-slf4j")

    }

    /**
     * Computes the complete set of target runtimes for each project.
     *
     * A project's computed target runtimes are the union of the required runtimes declared by
     * every project that transitively depends on that project. This ensures that if a project
     * which must be able to run on a certain set of runtimes depends on another project,
     * that other project must support the runtimes of the project with requirements.

            See <a href="https://s.apache.org/dependency-version">dependency version requirement documentation</a>
            and <a href="https://s.apache.org/transitive-dependencies-resolution">transitive dependencies resolution</a> for more details.
            ]]>
          </description>
          <type>String</type>
        </field>
        <field>
          <name>type</name>

order to a compiler.
</p>

<p>
Dependency analysis does not rely on the actual values of the
variables, only on lexical <i>references</i> to them in the source,
analyzed transitively. For instance, if a variable <code>x</code>'s
initialization expression refers to a function whose body refers to
variable <code>y</code> then <code>x</code> depends on <code>y</code>.
Specifically:
</p>

@SuppressWarnings("module")
module okhttp3 {
  requires transitive kotlin.stdlib;
  requires transitive okio;
  requires java.logging;
  exports okhttp3;
  exports okhttp3.internal to okhttp3.logging, okhttp3.sse, okhttp3.java.net.cookiejar, okhttp3.dnsoverhttps, mockwebserver3, okhttp3.mockwebserver, mockwebserver3.junit5, okhttp3.coroutines, okhttp3.tls;
  exports okhttp3.internal.concurrent to mockwebserver3, okhttp3.mockwebserver;

            if (!PROCESSOR_TYPE_IDS.contains(childType)) {
                continue;
            }
            for (DependencyNode transitive : child.getChildren()) {
                if (transitive.getArtifact() == null) {
                    continue;
                }
                String transitiveType = transitive.getArtifact().getProperty(ArtifactProperties.TYPE, "");
                String derived = DERIVE_MAP.get(transitiveType);

    if (enableValidation) {
      compileKotlinTask.source(file("src/main/java9"))
    }

    // Ignore warnings about using 'requires transitive' on automatic modules.
    // not needed when compiling with recent JDKs, e.g. 17
    options.compilerArgs.add("-Xlint:-requires-transitive-automatic")

    // Patch the compileKotlinJvm output classes into the compilation so exporting packages works correctly.
    options.compilerArgs.addAll(

    }

    protected DependencyManager getDependencyManager() {
        return getDependencyManager(true); // same default as in Maven4
    }

    public DependencyManager getDependencyManager(boolean transitive) {
        return transitive
                ? new TransitiveDependencyManager(getScopeManager())
                : new ClassicDependencyManager(getScopeManager());
    }

    protected DependencySelector getDependencySelector() {