import org.jetbrains.kotlin.gradle.tasks.KotlinCompile

/**
 * Encapsulates the configuration for the compilation of a source set, including:
 * - The target JVM version
 * - Workarounds which may affect the way the compilation is performed
 *
 * The compilation workarounds include:
 * - Using JDK internal classes
 * - Using Java standard library APIs that were introduced after the JVM version they are targeting

// it controls the JVM version of the compilation. This allows each source set within a project
// to compile to different JVM versions.

val jvmCompile = extensions.create<JvmCompileExtension>(JvmCompileExtension.NAME)

jvmCompile.compilations.configureEach {
    // Assume the compilation does not use any workarounds
    usesJdkInternals = false
    usesFutureStdlib = false

#!/bin/bash

set -e
# Enable tracing if set.
[ -n "$BASH_XTRACEFD" ] && set -x

function _init() {
	## All binaries are static make sure to disable CGO.
	export CGO_ENABLED=0

	## List of architectures and OS to test coss compilation.
	SUPPORTED_OSARCH="linux/ppc64le linux/mips64 linux/amd64 linux/arm64 linux/s390x darwin/arm64 darwin/amd64 freebsd/amd64 windows/amd64 linux/arm linux/386 netbsd/amd64 linux/mips openbsd/amd64 linux/riscv64"
}

    options.release = provider {
        throw GradleException("This task '${name}' is not associated with a compilation. Associate it with a compilation on the '${JvmCompileExtension.NAME}' extension.")
    }
}

val gradleModule = the<GradleModuleExtension>()
the<JvmCompileExtension>().apply {
    compilations {
        configureEach {
            // Everything compiles to Java 17 by default
            targetJvmVersion = 17

and there are no missing null checks.

## Decision

Use "NullAway" in JSpecify mode to check for null-related errors in Java code.

Consider improper uses of `null` detected by NullAway a compilation error (not a warning, and not a separate CI job to test).

Do not suppress NullAway errors without a justification.

import org.gradle.tooling.events.task.TaskOperationResult
import java.io.Serializable
import java.util.concurrent.CopyOnWriteArrayList

/**
 * Register a build service that monitors compilation tasks and code quality tasks (Checkstyle/CodeNarc/detekt)
 * and reports them as TeamCity build problems.
 */

#!/bin/bash

set -ex

function _init() {
	## All binaries are static make sure to disable CGO.
	export CGO_ENABLED=0
	export CRED_DIR="/media/${USER}/minio"

	## List of architectures and OS to test coss compilation.
	SUPPORTED_OSARCH="linux/ppc64le linux/amd64 linux/arm64"

	remote=$(git remote get-url upstream)
	if test "$remote" != "******@****.***:minio/minio.git"; then

/**
 * A BuildService which monitors a few tasks (in both build-logic and main build) and collects information for Build Scan.
 * It's currently implemented by two use cases:
 * 1. Collect cache misses for compilation tasks and publish a `CACHE_MISS` tag for a Build Scan.
 * 2. Collect failed task paths and display a link which points to the corresponding task in the Build Scan, like `https://ge.gradle.org/s/xxx/console-log?task=yyy`.
 */

 * <p>
 * This interface allows plugins and extensions to define and register additional path scopes
 * beyond the standard ones provided by Maven. Path scopes define how dependencies are used
 * in different contexts, such as compilation, testing, or runtime.
 * <p>
 * Implementations of this interface will be discovered through the Java ServiceLoader mechanism
 * and their provided path scopes will be available throughout the Maven build process.
 * <p>

        <dslContextParameter.branch>master</dslContextParameter.branch>
        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
        <!-- https://kotlinlang.org/docs/maven.html#enable-incremental-compilation -->
        <kotlin.compiler.incremental>true</kotlin.compiler.incremental>
    </properties>
    <groupId>Gradle_Check</groupId>
    <artifactId>Gradle_Check_dsl</artifactId>
    <version>1.0-SNAPSHOT</version>