That defines the metadata about the main response of a *path operation*.

You can also declare additional responses with their models, status codes, etc.

There's a whole chapter here in the documentation about it, you can read it at [Additional Responses in OpenAPI](additional-responses.md).

## OpenAPI Extra { #openapi-extra }

        Model model;
        try (InputStream is = getClass().getResourceAsStream("/xml/pom.xml")) {
            model = new MavenXpp3Reader().read(is);
        }

        // Serialize an inner child here so that the BaseObject.childrenTracking is non null
        Build build = model.getBuild();

        ByteArrayOutputStream baos = new ByteArrayOutputStream();
        try (ObjectOutputStream oos = new ObjectOutputStream(baos)) {

   * garbage-collected, even if there are no more instances of FinalizableReferenceQueue itself.
   * The code in FinalizableReferenceQueue goes to considerable trouble to ensure that there are
   * no such references and the tests here check that that trouble has not been in vain.
   *
   * When we reference FinalizableReferenceQueue in this test, we are referencing a class that is

    @Override
    public File translatePath(File path) {
        File result = path;

        if (path != null && basedir != null) {
            if (path.isAbsolute()) {
                // path is already absolute, we're done
            } else if (path.getPath().startsWith(File.separator)) {
                // drive-relative Windows path, don't align with base dir but with drive root
                result = path.getAbsoluteFile();

import org.gradle.api.provider.ProviderFactory;

import java.io.File;
import java.io.FileInputStream;
import java.io.IOException;
import java.io.InputStream;
import java.util.Properties;

// Define this here because we need it early.
public class VersionPropertiesLoader {
    static Properties loadBuildSrcVersion(File input, ProviderFactory providerFactory) throws IOException {
        Properties props = new Properties();

  /*
   * If you do this test from common.eventbus.EventBusTest, it doesn't actually test the behavior.
   * That is, even if exactly the same method works from inside the common.eventbus package tests,
   * it can fail here.
   */
  public void testAnonymous() {
    AtomicReference<String> holder = new AtomicReference<>();
    AtomicInteger deliveries = new AtomicInteger();
    EventBus bus = new EventBus();
    bus.register(

    display-name: "elastic / elasticsearch - pull request packaging-tests-windows-nojdk"
    description: "Testing of Elasticsearch pull requests - packaging-tests-windows-nojdk"
    # We use a hard-coded workspace directory here to avoid hitting windows path length limits
    child-workspace: "C:\\Users\\jenkins\\workspace\\pr-packaging-windows\\${BUILD_NUMBER}"
    project-type: matrix
    node: master
    scm:
      - git:

  }

  @Override
  ObjectCountHashMap<E> newBackingMap(int distinctElements) {
    return new ObjectCountLinkedHashMap<>(distinctElements);
  }

  // TODO(cpovirk): Should we have a serialVersionUID here?

    private final long length;
    private final int flags;

    /**
     * Constructs an SMB2 lock element with the specified parameters.
     *
     * @param offset the byte offset in the file where the lock begins
     * @param length the number of bytes to lock
     * @param flags the lock flags (combination of SMB2_LOCKFLAG_* constants)
     */
    public Smb2Lock(final long offset, final long length, final int flags) {

- [ ] Each commit in the pull request should have a meaningful subject line and body.
  Note that commits might be squashed by a maintainer on merge.
- [ ] Write unit tests that match behavioral changes, where the tests fail if the changes to the runtime are not applied.
  This may not always be possible but is a best-practice.
- [ ] Run `mvn verify` to make sure basic checks pass.