* under the License.
 */
package org.apache.maven.toolchain.java;

import java.nio.file.Files;
import java.nio.file.Path;
import java.nio.file.Paths;

import org.apache.maven.toolchain.DefaultToolchain;
import org.apache.maven.toolchain.model.ToolchainModel;
import org.apache.maven.utils.Os;
import org.slf4j.Logger;

/**
 * JDK toolchain implementation.
 *

    <dependency>
      <groupId>org.apache.maven</groupId>
      <artifactId>maven-api-settings</artifactId>
    </dependency>
    <dependency>
      <groupId>org.apache.maven</groupId>
      <artifactId>maven-api-toolchain</artifactId>
    </dependency>
    <dependency>
      <groupId>org.apache.maven</groupId>
      <artifactId>maven-api-plugin</artifactId>
    </dependency>
    <dependency>
      <groupId>org.apache.maven</groupId>

module github.com/minio/minio/docs/debugging/inspect

go 1.23.0

toolchain go1.24.8

require (
	github.com/klauspost/compress v1.17.11
	github.com/klauspost/filepathx v1.1.1
	github.com/minio/colorjson v1.0.8
	github.com/minio/madmin-go/v3 v3.0.88
	github.com/secure-io/sio-go v0.3.1
	github.com/tinylib/msgp v1.2.5
)

require (
	github.com/cespare/xxhash/v2 v2.3.0 // indirect
	github.com/fatih/color v1.18.0 // indirect

    <dependency>
      <groupId>org.apache.maven</groupId>
      <artifactId>maven-api-spi</artifactId>
    </dependency>
    <dependency>
      <groupId>org.apache.maven</groupId>
      <artifactId>maven-api-toolchain</artifactId>
    </dependency>
    <dependency>
      <groupId>org.apache.maven</groupId>
      <artifactId>maven-api-xml</artifactId>
    </dependency>

    <!-- Maven4 impl -->
    <dependency>

its value is derived from three sources:
the defaults for the Go toolchain used to build the program,
amended to match the Go version listed in `go.mod`,
and then overridden by explicit `//go:debug` lines in the program.

The [GODEBUG History](#history) gives the exact defaults for each Go toolchain version.
For example, Go 1.21 introduces the `panicnil` setting,
controlling whether `panic(nil)` is allowed;

3. Regarding the Tooling API client, it is the responsibility of the application embedding it to provide the Java runtime.

## Consequences

- Finalize Daemon JVM toolchain support, including auto-provisioning.
- To stop requiring a pre-installed Java runtime for the Gradle Wrapper and Launcher, Gradle will need to find an alternative.

pattern="$1"
if [ "$pattern" = "" ]; then
	pattern=.
fi

./make.bash || exit 1
GOROOT="$(cd .. && pwd)"

gettargets() {
	../bin/go tool dist list | sed -e 's|/|-|' |
		grep -E -v '^(android|ios)' # need C toolchain even for cross-compiling
	echo linux-arm-arm5
}

selectedtargets() {
	gettargets | grep -E "$pattern"
}

# put linux first in the target list to get all the architectures up front.
linux_targets() {

    <module>maven-api-di</module>
    <module>maven-api-xml</module>
    <module>maven-api-model</module>
    <module>maven-api-plugin</module>
    <module>maven-api-settings</module>
    <module>maven-api-toolchain</module>
    <module>maven-api-metadata</module>
    <module>maven-api-core</module>
    <module>maven-api-spi</module>
    <module>maven-api-cli</module>
  </modules>

  <properties>

   * gets translated back to `Integer.valueOf` because that is the only thing J2KT can support. And
   * anyway, it's nice to avoid `Integer.valueOf` because the Android toolchain optimizes multiple
   * `Integer.valueOf` calls into one! So we stick with the deprecated `Integer` constructor.
   */

  public void testEqualsEquivalent() {
    EquivalenceTester.of(Equivalence.equals())

You can then replace the existing file with this new downloaded version. 
### Java Toolchain

The Gradle build uses [Java Toolchain](https://docs.gradle.org/current/userguide/toolchains.html) support to compile and execute tests across multiple versions of Java.