*
     * @return {@code true} if the dependency management information should be retrieved, {@code false} otherwise.
     */
    boolean isResolveManagedVersions();

    /**
     * Enables/disables resolution of the dependency management information.
     *
     * @param resolveManagedVersions {@code true} if the dependency management information should be retrieved, {@code

## Dependency Injection { #dependency-injection }

Using `BackgroundTasks` also works with the dependency injection system, you can declare a parameter of type `BackgroundTasks` at multiple levels: in a *path operation function*, in a dependency (dependable), in a sub-dependency, etc.

        this.plugin = plugin;
        setFile(pluginArtifact.getFile());
        setResolved(true);
    }

    @Override
    public List<Dependency> getDependencies() {
        return plugin.getDependencies();
    }

    @Override
    public List<Dependency> getManagedDependencies() {
        return Collections.emptyList();
    }

    // TODO: this is duplicate of MavenPluginArtifactHandlerProvider provided one

    }
)

client = TestClient(app)


def raise_value_error():
    raise ValueError()


def dependency_with_yield():
    yield raise_value_error()


@app.get("/dependency-with-yield", dependencies=[Depends(dependency_with_yield)])
def with_yield(): ...


@app.get("/http-exception")
def route_with_http_exception():
    raise HTTPException(status_code=400)

/**
 * A dependency injection framework for Maven that provides JSR-330 style annotations
 * for managing object lifecycle and dependencies within Maven's build process.
 * <p>
 * This package provides a set of annotations that control how objects are created,
 * managed and injected throughout Maven's execution lifecycle. The framework is designed
 * to be lightweight yet powerful, supporting various scopes of object lifecycle from

 ({{{./apidocs/org/apache/maven/repository/internal/MavenRepositorySystemUtils.html}javadoc}},
 {{{./xref/org/apache/maven/repository/internal/MavenRepositorySystemUtils.html}source}}).

``MinIO`` uses `go mod` to manage its dependencies.

- Run `go get foo/bar` in the source folder to add the dependency to `go.mod` file.

To remove a dependency

- Edit your code and remove the import reference.
- Run `go mod tidy` in the source folder to remove dependency from `go.mod` file.

### What are the coding guidelines for MinIO?

This document formally describes the process of addressing and managing a
reported vulnerability that has been found in the MinIO server code base,
any directly connected ecosystem component or a direct / indirect dependency
of the code base.

## Scope

The vulnerability management policy described in this document covers the
process of investigating, assessing and resolving a vulnerability report

 * <p>
 * Key components include:
 * <ul>
 *   <li>{@link org.apache.maven.api.model.Model} - The root element of a POM file</li>
 *   <li>{@link org.apache.maven.api.model.Dependency} - Represents a project dependency</li>
 *   <li>{@link org.apache.maven.api.model.Plugin} - Represents a Maven plugin configuration</li>
 *   <li>{@link org.apache.maven.api.model.Build} - Contains build configuration information</li>

import java.util.Date;
import java.util.HashMap;
import java.util.Iterator;
import java.util.List;
import java.util.Map;
import java.util.Properties;
import java.util.TimeZone;

import org.apache.maven.model.Dependency;
import org.apache.maven.model.Model;
import org.apache.maven.model.Resource;
import org.apache.maven.model.building.DefaultModelBuildingRequest;
import org.apache.maven.model.building.ModelBuildingRequest;