- [Server Binaries](#server-binaries)
    - [Node Binaries](#node-binaries)
    - [Container Images](#container-images)
  - [Changelog since v1.21.13](#changelog-since-v12113)
  - [Dependencies](#dependencies)
    - [Added](#added)
    - [Changed](#changed)
    - [Removed](#removed)
- [v1.21.13](#v12113)
  - [Downloads for v1.21.13](#downloads-for-v12113)
    - [Source Code](#source-code-1)

*temporal* response to extract the status code (also cookies and headers), and will put them in the final response that contains the value you returned, filtered by any `response_model`.

You can also declare the `Response` parameter in dependencies, and set the status code in them. But keep in mind that the last one to be set will win....

import okhttp3.buildsupport.testJavaVersion

plugins {
  id("okhttp.base-conventions")
  id("java")
  id("application")
  alias(libs.plugins.jlink)
  alias(libs.plugins.extra.java.module.info)
}

dependencies {
  implementation(projects.okhttp)
  implementation(projects.loggingInterceptor)

  // Force version 26.0.2-1 which is a proper JPMS module, unlike transitive 13.0
  implementation(libs.jetbrains.annotations)

    private final CoreExtension extension;

    public ExtensionResolutionException(CoreExtension extension, Throwable cause) {
        super(
                "Extension " + extension.getId() + " or one of its dependencies could not be resolved: "
                        + cause.getMessage(),
                cause);
        this.extension = extension;
    }

    public CoreExtension getExtension() {
        return extension;

            plugins {
             id 'java'
             id 'elasticsearch.test-base'
            }

            repositories {
                mavenCentral()
            }

            dependencies {
                testImplementation 'junit:junit:4.12'
            }

            tasks.named('test').configure {
                nonInputProperties.systemProperty("foo", project.getProperty('foo'))
            }

  - [Changelog since v1.23.16](#changelog-since-v12316)
  - [Changes by Kind](#changes-by-kind)
    - [Feature](#feature)
    - [Bug or Regression](#bug-or-regression)
  - [Dependencies](#dependencies)
    - [Added](#added)
    - [Changed](#changed)
    - [Removed](#removed)
- [v1.23.16](#v12316)
  - [Downloads for v1.23.16](#downloads-for-v12316)
    - [Source Code](#source-code-1)

### Bağımlılıklar { #dependencies }

Aynısı [bağımlılıklar](tutorial/dependencies/index.md) için de geçerlidir. Bir bağımlılık `async def` yerine standart bir `def` fonksiyonuysa, harici thread pool’da çalıştırılır.

### Alt-bağımlılıklar { #sub-dependencies }

        SourceSet yamlTestSourceSet = sourceSets.create(SOURCE_SET_NAME);

        registerTestTask(project, yamlTestSourceSet);

        // setup the dependencies
        setupTestDependenciesDefaults(project, yamlTestSourceSet);

        // setup the copy for the rest resources
        project.getTasks().withType(CopyRestApiTask.class).configureEach(copyRestApiTask -> {

      </excludes>
    </fileSet>
    <fileSet>
      <directory>${project.build.directory}/maven-shared-archive-resources/META-INF</directory>
      <outputDirectory>/</outputDirectory>
      <includes>
        <include>DEPENDENCIES</include>
        <!-- exclude the license and notice as they are not as accurate as the ones from above -->
      </includes>
    </fileSet>
  </fileSets>

 * <p>
 * This interface allows plugins and extensions to define and register additional path scopes
 * beyond the standard ones provided by Maven. Path scopes define how dependencies are used
 * in different contexts, such as compilation, testing, or runtime.
 * <p>
 * Implementations of this interface will be discovered through the Java ServiceLoader mechanism