<packaging>pom</packaging>

  <name>Simple Unit Test Parent</name>

  <dependencyManagement>
    <dependencies>
      <dependency>
        <groupId>ut.simple</groupId>
        <artifactId>dependency</artifactId>
        <version>1.0</version>
      </dependency>
    </dependencies>
  </dependencyManagement>

     * to "pull in" transitive dependencies of eliminated projects, as for case above, the properly filtered list would
     * be {@code a -> c}.
     * <p>
     * Original code would falsely report {@code a} project as "without dependencies", basically would lose link due
     * filtering. This causes build ordering issues in concurrent builders.
     */

    header_params: list[ModelField] = field(default_factory=list)
    cookie_params: list[ModelField] = field(default_factory=list)
    body_params: list[ModelField] = field(default_factory=list)
    dependencies: list["Dependant"] = field(default_factory=list)
    name: str | None = None
    call: Callable[..., Any] | None = None
    request_param_name: str | None = None
    websocket_param_name: str | None = None

      - name: Setup uv
        uses: astral-sh/setup-uv@v7
        with:
          enable-cache: true
          cache-dependency-glob: |
            pyproject.toml
            uv.lock
      - name: Install Dependencies
        run: uv sync --no-dev --group tests --extra all
      - name: Ensure that we have the lowest supported Pydantic version
        if: matrix.uv-resolution == 'lowest-direct'

When you install with `pip install "fastapi[standard]"` it comes with some default optional standard dependencies, including `fastapi-cloud-cli`, which allows you to deploy to [FastAPI Cloud](https://fastapicloud.com).

If you don't want to have those optional dependencies, you can instead install `pip install fastapi`.

     * resolving plugin dependencies and executing plugin goals that participate in project building.
     *
     * @return true if plugins should be processed, false otherwise
     */
    boolean isProcessPlugins();

    /**
     * Gets the list of remote repositories to use for resolving dependencies during project building.

tasks.named("assemble").configure { enabled = false }
archivesBaseName = 'elasticsearch-benchmarks'

tasks.named("test").configure { enabled = false }

configurations {
  expression
  painless
}

dependencies {
  api(project(":server")) {
    // JMH ships with the conflicting version 4.6. This prevents us from using jopt-simple in benchmarks (which should be ok) but allows
    // us to invoke the JMH uberjar as usual.

* Even dependencies can have dependencies, creating a hierarchy or **"graph" of dependencies**.
* All **automatically handled** by the framework.
* All the dependencies can require data from requests and **augment the path operation** constraints and automatic documentation.
* **Automatic validation** even for *path operation* parameters defined in dependencies.

    is not the same as the module itself.
  </description>
  <dependencies>
    <dependency>
      <groupId>com.example.group</groupId>
      <artifactId>testvalidpom</artifactId>
      <version>0.0.1-SNAPSHOT</version>
      <classifier>linux</classifier>
    </dependency>
  </dependencies>

    dependency is the same as the module itself.
  </description>
  <dependencies>
    <dependency>
      <groupId>com.example.group</groupId>
      <artifactId>testinvalidpom</artifactId>
      <version>0.0.1-SNAPSHOT</version>
    </dependency>
  </dependencies>