// 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.

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>

            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);

    }

    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() {

    byte[] b3 = "????".getBytes(Charsets.US_ASCII);
    byte[] b4 = "ニュース".getBytes(Charsets.US_ASCII);
    byte[] b5 = "スューー".getBytes(Charsets.US_ASCII);
    // Assert they are all equal (using the transitive property)
    assertThat(b1).isEqualTo(b2);
    assertThat(b2).isEqualTo(b3);
    assertThat(b3).isEqualTo(b4);
    assertThat(b4).isEqualTo(b5);
  }

    byte[] b3 = "????".getBytes(Charsets.US_ASCII);
    byte[] b4 = "ニュース".getBytes(Charsets.US_ASCII);
    byte[] b5 = "スューー".getBytes(Charsets.US_ASCII);
    // Assert they are all equal (using the transitive property)
    assertThat(b1).isEqualTo(b2);
    assertThat(b2).isEqualTo(b3);
    assertThat(b3).isEqualTo(b4);
    assertThat(b4).isEqualTo(b5);
  }

     */
    public static final String CONSTITUTES_BUILD_PATH = "constitutesBuildPath";

    /**
     * When an artifact is both a regular dependency and a transitive dependency
     * of a processor, this property records the derived processor type ID.
     *
     * @since 4.0.0
     */
    public static final String PROCESSOR_TYPE = "maven.processor.type";

    /**

# Tensorflow to the default, however test coverage wasn't enough to catch the
# errors.
# There is ongoing work on Bazel team's side to provide support for transitive
# shared libraries. As part of migrating to transitive shared libraries, we
# hope to provide a better mechanism for control over symbol exporting, and
# then tackle this issue again.
#

        (for num > 1)
    *   Added top-k to precision and recall to keras metrics.
    *   Add a ragged size op and register it to the op dispatcher
    *   Transitive dependencies on :`pooling_ops` were removed. Some users may
        need to add explicit dependencies on :`pooling_ops` if they reference
        the operators from that library.
    *   Add `CompositeTensor` base class.