import org.junit.jupiter.api.Test
import org.junit.jupiter.api.extension.RegisterExtension

/**
 * Java HTTP Client.
 *
 * https://openjdk.java.net/groups/net/httpclient/intro.html
 *
 * Baseline test if we ned to validate OkHttp behaviour against other popular clients.
 */
class JavaHttpClientTest {
  @JvmField @RegisterExtension
  val platform = PlatformRule()

  @Test fun get(server: MockWebServer) {

import static org.junit.Assert.assertThat;

import java.sql.SQLException;
import java.util.Locale;

import org.codelibs.core.misc.LocaleUtil;
import org.junit.After;
import org.junit.Before;
import org.junit.Test;

/**
 * @author manhole
 */
public class SQLRuntimeExceptionTest {

    @Before
    public void setUp() throws Exception {
        LocaleUtil.setDefault(() -> Locale.JAPANESE);
    }

    @After

 * See the License for the specific language governing permissions and
 * limitations under the License.
 */

package com.google.common.collect.testing;

import junit.framework.Test;
import junit.framework.TestCase;
import junit.framework.TestSuite;

/**
 * Suite of tests for OpenJdk 6 tests. The existence of this class is a hack because the

    <scope name="Gradle public API"

	baseTestCases := []TestSuiteCommon{
		// Init and run test on ErasureSD backend with signature v4.
		{serverType: "ErasureSD", signer: signerV4},
		// Init and run test on ErasureSD backend, with tls enabled.
		{serverType: "ErasureSD", signer: signerV4, secure: true},
		// Init and run test on Erasure backend.
		{serverType: "Erasure", signer: signerV4},
		// Init and run test on ErasureSet backend.

  compileOnly(libs.findbugs.jsr305)

  testImplementation(projects.okhttpTestingSupport)
  testImplementation(libs.conscrypt.openjdk)
  testImplementation(libs.junit)
  testImplementation(libs.kotlin.test.common)
  testImplementation(libs.kotlin.test.junit)
  testImplementation(libs.assertk)
}

mavenPublishing {
  configure(KotlinJvm(javadocJar = JavadocJar.Empty()))

  <name>p2</name>
  <version>1.0</version>
  <scm>
    <url>scm-url</url>
  </scm>

  <dependencies>

    <dependency>
      <groupId>maven-test</groupId>
      <artifactId>t09-a</artifactId>
    </dependency>

    <dependency>
      <groupId>maven-test</groupId>
      <artifactId>t09-d</artifactId>
      <version>1.0</version>
    </dependency>

  </dependencies>

  <build>
    <plugins>

  <name>p1</name>
  <version>1.0</version>
  <scm>
    <url>scm-url</url>
  </scm>

  <dependencies>

    <dependency>
      <groupId>maven-test</groupId>
      <artifactId>t10-a</artifactId>
    </dependency>

    <dependency>
      <groupId>maven-test</groupId>
      <artifactId>t10-c</artifactId>
      <scope>runtime</scope>
    </dependency>

  </dependencies>

  <build>
    <plugins>

# Finally: Run your script of choice.
#   If you've clicked on a test result from our CI (via a dashboard or GitHub link),
#   click to "Invocation Details" and find BUILD_CONFIG, which will contain a
#   "build_file" item that indicates the script used.
ci/official/wheel.sh

# Advanced: Select specific build/test targets with "any.sh".
# TF_ANY_TARGETS=":your/target" TF_ANY_MODE="test" ci/official/any.sh

        build/report-* => $hiddenArtifactDestination
        build/tmp/teŝt files/** => $hiddenArtifactDestination/teŝt-files
        build/errorLogs/** => $hiddenArtifactDestination/errorLogs
        subprojects/internal-build-reports/build/reports/incubation/all-incubating.html => incubation-reports
        testing/architecture-test/build/reports/binary-compatibility/report.html => binary-compatibility-reports