Docker Compose allows defining and running single host, multi-container Docker applications.

 * in the list of remote repositories. This is done either explicitly using the
 * {@link org.apache.maven.api.services.VersionResolver VersionResolver} service, or implicitly when resolving
 * an artifact.</p>
 *
 * <p><dfn>Artifact resolution</dfn> is the process of {@linkplain org.apache.maven.api.services.VersionResolver
 * resolving the version} and then downloading the file.</p>
 *

import org.apache.maven.api.services.BuilderProblem;
import org.apache.maven.api.services.Lookup;
import org.apache.maven.api.services.MavenException;
import org.apache.maven.api.services.MessageBuilder;
import org.apache.maven.api.services.SettingsBuilder;
import org.apache.maven.api.services.SettingsBuilderRequest;
import org.apache.maven.api.services.SettingsBuilderResult;
import org.apache.maven.api.services.Sources;

distributionBase=GRADLE_USER_HOME
distributionPath=wrapper/dists
distributionUrl=https\://services.gradle.org/distributions/gradle-7.2-all.zip
zipStoreBase=GRADLE_USER_HOME
zipStorePath=wrapper/dists

# To run locally an OpenLDAP instance using Docker
# $ docker-compose -f ldap.yaml up -d
version: '3.7'

services:
  openldap:
    image: quay.io/minio/openldap
    ports:
      - "389:389"
      - "636:636"
    environment:
      LDAP_ORGANIZATION: "MinIO Inc"
      LDAP_DOMAIN: "min.io"

OkHttp Container Tests
======================

This module contains tests against other services

                    "-Porg.gradle.java.installations.auto-download=false",
                ).joinToString(" "),
        )

        setArtifactRules(
            """$artifactRules
platforms/core-runtime/base-services/build/generated-resources/build-receipt/org/gradle/build-receipt.properties
""",
        )
    }) {
    companion object {
        fun buildTypeId(model: CIBuildModel) = buildTypeId(model.projectId)

Each process, or "runtime", applies different constraints to the code that runs in that process.
For example, each process has different supported JVMs and a different set of services available for dependency injection.
While a lot of Gradle source code runs only in the Gradle daemon, not all of it does so.

 * and control over the build environment, enabling developers to specify
 * the exact versions of tools they wish to use.</p>
 *
 * <p>
 * Toolchains can be obtained through the {@link org.apache.maven.api.services.ToolchainManager ToolchainManager}
 * service. This service provides methods to retrieve and manage toolchains defined
 * in the Maven configuration.
 * </p>
 *
 * <p>

import org.gradle.api.file.FileSystemOperations
import org.gradle.api.internal.tasks.testing.results.serializable.SerializableTestResultStore
import org.gradle.api.provider.Provider
import org.gradle.api.services.BuildService
import org.gradle.api.services.BuildServiceParameters
import org.gradle.api.tasks.testing.TestResult
import org.gradle.internal.exceptions.DefaultMultiCauseException
import org.gradle.tooling.events.FinishEvent