rm -rf ~/.m2/jdks/ ~/.m2/toolchains.xml
            (But don't run that if you have put something into ~/.m2/toolchains.xml yourself.)
            -->
            <execution>
              <id>download-24-and-surefire-version</id>
              <goals>
                <goal>toolchain</goal>
              </goals>
              <configuration>
                <toolchains>
                  <jdk>

            rm -rf ~/.m2/jdks/ ~/.m2/toolchains.xml
            (But don't run that if you have put something into ~/.m2/toolchains.xml yourself.)
            -->
            <execution>
              <id>download-24-and-surefire-version</id>
              <goals>
                <goal>toolchain</goal>
              </goals>
              <configuration>
                <toolchains>
                  <jdk>

                                    <la:link href="downloadpage"
                                             styleClass="btn btn-primary btn-xs">
                                        <em class="fa fa-download">
                                        <la:message key="labels.bad_word_link_download"/>
                                    </la:link>
                                    <la:link href="uploadpage"

                                        <la:link href="../downloadpage"
                                                 styleClass="btn btn-primary btn-xs">
                                            <em class="fa fa-download">
                                            <la:message
                                                    key="labels.bad_word_link_download"/>
                                        </la:link>

                                        <la:link href="../downloadpage"
                                                 styleClass="btn btn-primary btn-xs">
                                            <em class="fa fa-download">
                                            <la:message
                                                    key="labels.bad_word_link_download"/>
                                        </la:link>

	unset MINIO_KMS_AUTO_ENCRYPTION # do not auto-encrypt objects
	export MINIO_CI_CD=1

	MC_BUILD_DIR="mc-$RANDOM"
	if ! git clone --quiet https://github.com/minio/mc "$MC_BUILD_DIR"; then
		echo "failed to download https://github.com/minio/mc"
		purge "${MC_BUILD_DIR}"
		exit 1
	fi

	(cd "${MC_BUILD_DIR}" && go build -o "$WORK_DIR/mc")

	# remove mc source.
	purge "${MC_BUILD_DIR}"

      # When we specify multiple JDKs, the final one becomes the default, which is used to execute Maven itself.
      # Our Maven configuration then specifies different JDKs to use for some of the steps:
      # - 11 (sometimes) to *download* to support anyone who runs JDiff or our Gradle integration tests (including our doc snapshots and our Java 11 CI test run) but not to use directly

                                    name="downloadLogs"
                                    value="<la:message key="labels.download_diagnostic_logs_button"/>">
                                <em class="fa fa-download">
                                <la:message key="labels.download_diagnostic_logs_button"/>
                            </button>
                        </div>
                    </div>
                </div>

	"github.com/valyala/bytebufferpool"
)

const (
	envMinisignPubKey = "MINIO_UPDATE_MINISIGN_PUBKEY"
	updateTimeout     = 10 * time.Second
)

var (
	// Newer official download info URLs appear earlier below.
	minioReleaseInfoURL = MinioReleaseURL + "minio.sha256sum"

	// For windows our files have .exe additionally.
	minioReleaseWindowsInfoURL = MinioReleaseURL + "minio.exe.sha256sum"
)

                                        <la:link href="../downloadpage/${f:u(dictId)}"
                                                 styleClass="btn btn-primary btn-xs">
                                            <em class="fa fa-download">
                                            <la:message key="labels.dict_protwords_link_download"/>
                                        </la:link>