protected static final String START_URLS = "start_urls";

    /** XML element name for good (included) URLs configuration. */
    protected static final String GOOD_URLS = "good_urls";

    /** XML element name for bad (excluded) URLs configuration. */
    protected static final String BAD_URLS = "bad_urls";

    /** Array of supported web protocols for URL classification. */
    protected String[] webProtocols = { "http:", "https:" };

   */
  HTTP_1_0("http/1.0"),

  /**
   * A plaintext framing that includes persistent connections.
   *
   * This version of OkHttp implements [RFC 7230][rfc_7230], and tracks revisions to that spec.
   *
   * [rfc_7230]: https://tools.ietf.org/html/rfc7230
   */
  HTTP_1_1("http/1.1"),

  /**
   * Chromium's binary-framed protocol that includes header compression, multiplexing multiple

<module>
<source path="">
  <!-- Hack to keep collect from hiding collect.testing supersource: -->
  <exclude name="**/testing/**"/>
</source>

<!--
    We used to set this only for packages that had manual supersource. That
    worked everywhere that I know of except for one place: when running the GWT
    util.concurrent tests under Guava.

    The problem is that GWT responds poorly to two .gwt.xml files in the same
    Java package; see

license is intended to facilitate the commercial use of the Program,
the Contributor who includes the Program in a commercial product
offering should do so in a manner which does not create potential
liability for other Contributors. Therefore, if a Contributor includes
the Program in a commercial product offering, such Contributor
("Commercial Contributor") hereby agrees to defend and indemnify every

        source.put("url", "https://example.com/page.html");
        source.put("title", "Test");
        source.put("content", "Body");
        source.put("cache", "should be excluded");
        source.put("host", "example.com");

        indexExportJob.exportDocument(source, tempDir.toString(), Set.of("cache"), new HtmlIndexExportFormatter());

<module>
<source path="">
  <!-- Hack to keep collect from hiding collect.testing supersource: -->
  <exclude name="**/testing/**"/>
</source>

<!--
    We used to set this only for packages that had manual supersource. That
    worked everywhere that I know of except for one place: when running the GWT
    util.concurrent tests under Guava.

    The problem is that GWT responds poorly to two .gwt.xml files in the same
    Java package; see

<module>
<source path="">
  <!-- Hack to keep collect from hiding collect.testing supersource: -->
  <exclude name="**/testing/**"/>
</source>

<!--
    We used to set this only for packages that had manual supersource. That
    worked everywhere that I know of except for one place: when running the GWT
    util.concurrent tests under Guava.

    The problem is that GWT responds poorly to two .gwt.xml files in the same
    Java package; see

    implementation(buildLibs.gradleGuidesPlugin)
    implementation(buildLibs.javaParserCore)
    implementation(buildLibs.guava)
    implementation(buildLibs.jhighlight) {
        exclude(module = "servlet-api")
    }
    implementation(buildLibs.flexmark)
    implementation(buildLibs.gson)
    implementation(buildLibs.commonsLang3)
    implementation(buildLibs.asciidoctor)

        uses: gradle/actions/setup-gradle@v6
        with:
          cache-read-only: ${{ github.ref != 'refs/heads/master' }}
      - run: ./gradlew ${{ matrix.bucket.tasks }} -DdisableLocalCache=true -PflakyTests=exclude ${{ needs.build.outputs.sys-prop-args }}

  unit-test-windows-arm:
    name: "Unit Test Windows ARM"
    permissions:
      contents: read
    runs-on: windows-11-arm
    needs: build
    defaults:

<module>
<source path="">
  <!-- Hack to keep collect from hiding collect.testing supersource: -->
  <exclude name="**/testing/**"/>
</source>

<!--
    We used to set this only for packages that had manual supersource. That
    worked everywhere that I know of except for one place: when running the GWT
    util.concurrent tests under Guava.

    The problem is that GWT responds poorly to two .gwt.xml files in the same
    Java package; see