<artifactId>maven-compat-modules</artifactId>
    <version>4.1.0-SNAPSHOT</version>
  </parent>

  <artifactId>maven-settings</artifactId>

  <name>Maven Settings</name>
  <description>Maven Settings model.</description>

  <dependencies>
    <dependency>
      <groupId>org.apache.maven</groupId>
      <artifactId>maven-api-settings</artifactId>
    </dependency>
    <dependency>

* `version`: The version of your API, e.g. `2.5.0`.
* `openapi_version`: The version of the OpenAPI specification used. By default, the latest: `3.1.0`.
* `summary`: A short summary of the API.
* `description`: The description of your API, this can include markdown and will be shown in the docs.
* `routes`: A list of routes, these are each of the registered *path operations*. They are taken from `app.routes`.

/// info

app = FastAPI()


@app.post("/files/")
async def create_files(
    files: Annotated[list[bytes], File(description="Multiple files as bytes")],
):
    return {"file_sizes": [len(file) for file in files]}


@app.post("/uploadfiles/")
async def create_upload_files(
    files: Annotated[
        list[UploadFile], File(description="Multiple files as UploadFile")
    ],
):
    return {"filenames": [file.filename for file in files]}

응답의 콘텐츠 타입은 `application/json` 대신 `application/jsonl`이고, 본문은 다음과 같습니다:

```json
{"name": "Plumbus", "description": "A multi-purpose household device."}
{"name": "Portal Gun", "description": "A portal opening device."}
{"name": "Meeseeks Box", "description": "A box that summons a Meeseeks."}
```

JSON 배열(Python의 list에 해당)과 매우 비슷하지만, 항목들을 `[]`로 감싸고 항목 사이에 `,`를 넣는 대신, 줄마다 하나의 JSON 객체가 있고, 새 줄 문자로 구분됩니다.

            td { link(linkend: blockDoc.id) { literal("$blockName { }")} }
            td(blockDoc.description)
        }
    }

    def mergeTypes(Element typeTable, DslDocModel model) {
        typeTable.addFirst {
            thead {
                tr {
                    td('Type')
                    td('Description')
                }
            }
        }

        typeTable.tr.each { Element tr ->

  <groupId>inheritance</groupId>
  <artifactId>parent</artifactId>
  <version>11-SNAPSHOT</version>

  <name>Model urls inheritance test parent</name>
  <description>Flat directory structure case: module = ../child directory path + child directory path != child-artifact-id</description>

  <modules>
    <module>../inheritance</module><!-- current directory == inheritance -->
  </modules>

name: Reusable Build
on:
  workflow_call:
    inputs:
      runner:
        description: 'Which runner should the workflow run on?'
        required: true
        type: string
      tfci:
        description: 'TFCI environment variable'
        required: true
        type: string

permissions:
  contents: read

jobs:
  build-and-test:

 * such as those associated with files and directories. The Windows OS
 * determines which users have the necessary permissions to access objects
 * based on these entries.
 * <p>
 * To fully understand the information exposed by this class a description
 * of the access check algorithm used by Windows is required. The following
 * is a basic description of the algorithm. For a more complete description

{"attributes":{"description":"","kibanaSavedObjectMeta":{"searchSourceJSON":"{\"query\":{\"query\":\"\",\"language\":\"kuery\"},\"filter\":[],\"indexRefName\":\"kibanaSavedObjectMeta.searchSourceJSON.index\"}"},"title":"search-query-counts-per-sec","uiStateJSON":"{}","ver...

  <groupId>inheritance</groupId>
  <artifactId>child-artifact-id</artifactId>
  <version>11-SNAPSHOT</version>
  <name>Model urls inheritance test child</name>
  <description>Flat directory structure case: module = ../child-artifact-id + child directory path != child-artifact-id</description>

  <!-- 5 inherited urls with ../${project.artifactId} added to parent -->
  <url>http://www.apache.org/path/to/parent/../child-artifact-id/</url>
  <scm>