### Package Requirements { #package-requirements }

You would normally have the **package requirements** for your application in some file.

It would depend mainly on the tool you use to **install** those requirements.

The most common way to do it is to have a file `requirements.txt` with the package names and their versions, one per line.

    <img src="https://img.shields.io/badge/Docs-Gradle%20User%20Guide-blueviolet?style=flat&logo=read-the-docs" alt="Gradle Documentation">
  </a>
</div>


## 🐘 **Gradle Build Tool** 

                    .longOpt(ENC)
                    .desc("Launch the Maven Encryption tool (script option).")
                    .get());
            options.addOption(Option.builder()
                    .longOpt(UPGRADE)
                    .desc("Launch the Maven Upgrade tool (script option).")
                    .get());
            options.addOption(Option.builder()

                    },
                }
            ]
        }
    )


def test_header_param_model_extra(client: TestClient):
    response = client.get(
        "/items/", headers=[("save-data", "true"), ("tool", "plumbus")]
    )
    assert response.status_code == 200, response.text
    assert response.json() == snapshot(
        {
            "host": "testserver",
            "save_data": True,

	}
	reset := func() {
		bf.Reset()
	}

	ret := make(map[time.Duration][]string)

	s := bufio.NewScanner(f)
	s.Split(bufio.ScanLines)

	var (
		t            time.Duration
		skip, record bool
	)

	for s.Scan() {
		line := s.Text()
		switch {
		case skip && line != "":
		case skip && line == "":
			skip = false
		case record && line == "":
			stackTrace := bf.String()
			reset()

    MavenProject build(File pom, ProjectBuilderConfiguration configuration) throws ProjectBuildingException;

    // TODO maven-site-plugin -- not used by the plugin directly, but used by Doxia Integration Tool & MPIR
    // see DOXIASITETOOLS-167 & MPIR-349
    MavenProject build(File pom, ArtifactRepository localRepository, ProfileManager profileManager)
            throws ProjectBuildingException;

META-INF/MANIFEST.MF Manifest-Version: 1.0 Archiver-Version: Plexus Archiver Created-By: Apache Maven Built-By: Brett Build-Jdk: 1.5.0_04 Extension-Name: maven-plugin-api Specification-Title: Maven is a project development management and com prehension tool. Based on the concept of a project object model: buil ds, dependency management, documentation creation, site publication, and distribution publication are all controlled from the declarative file. Maven can be extended by plugins to utilise a number...

- **Java Version**: 17+
- **Dependencies**:
  - Apache Commons IO 2.19.0 (runtime)
  - JUnit 4.13.2 (test)
- **Module Name**: `org.codelibs.curl4j`
- **Package Structure**: `org.codelibs.curl.*`
- **Build Tool**: Maven 3.x
- **Test Coverage**: JaCoCo plugin enabled

## Code Style

- Uses external Eclipse formatter configuration from CodeLibs
- Apache License 2.0 headers on all source files (updated to 2025)

import org.apache.maven.api.annotations.Nonnull;

/**
 * Service interface for managing Maven toolchains, which provide abstraction for different
 * build tools and environments.
 *
 * <p>A toolchain represents a specific build tool configuration (e.g., JDK, compiler) that can be
 * used during the Maven build process. This service allows for retrieving, storing, and managing
 * these toolchains.</p>
 *
 * @since 4.0.0
 */
@Experimental

import org.apache.maven.api.annotations.Experimental;
import org.apache.maven.api.annotations.Nonnull;
import org.apache.maven.api.cli.Options;

/**
 * Defines the options specific to the Maven upgrade tool.
 * This interface extends the general {@link Options} interface, adding upgrade-specific configuration options.
 *
 * @since 4.0.0
 */
@Experimental
public interface UpgradeOptions extends Options {
    /**