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

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

                                    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>

# above the location of this file (setup.sh). We could also use "git rev-parse
# --show-toplevel", but that wouldn't work for non-git repos (like if someone
# downloaded TF as a zip archive).
export TFCI_GIT_DIR=$(cd $(dirname "$0"); realpath ../../)
cd "$TFCI_GIT_DIR"

# "TFCI" may optionally be set to the name of an env-type file with TFCI

    /**
     * @return repositories of this node
     */
    @Nonnull
    List<RemoteRepository> getRemoteRepositories();

    /**
     * The repository where this artifact has been downloaded from.
     */
    @Nonnull
    Optional<RemoteRepository> getRepository();

    /**
     * Traverses this node and potentially its children using the specified visitor.
     *

Clicking okay on the dialog will cause a copy of the `accepted-public-api-changes.json` containing your (properly sorted) addition to be downloaded.
You can then replace the existing file with this new downloaded version. 
### Java Toolchain

            }
          ]]></code>
        </codeSegment>
      </codeSegments>
    </class>

    <class>
      <name>RepositoryPolicy</name>
      <version>1.0.0</version>
      <description>Download policy</description>
      <fields>
        <field>
          <name>enabled</name>
          <version>1.0.0</version>

TEST_MINIO_ENC_KEY="MDEyMzQ1Njc4OTAxMjM0NTY3ODkwMTIzNDU2Nzg5MDA"

# Create certificates for TLS enabled MinIO
echo -n "Setup certs for MinIO instances ..."
wget -O certgen https://github.com/minio/certgen/releases/latest/download/certgen-linux-amd64 && chmod +x certgen
./certgen --host localhost
mkdir -p /tmp/certs
mv public.crt /tmp/certs || sudo mv public.crt /tmp/certs
mv private.key /tmp/certs || sudo mv private.key /tmp/certs
echo "done"

labels.dict_stemmeroverride_link_delete=Löschen
labels.dict_stemmeroverride_link_details=Details
labels.dict_stemmeroverride_link_download=Download
labels.dict_stemmeroverride_link_upload=Upload
labels.dict_stemmeroverride_source=Quelle
labels.dict_stemmeroverride_target=Ziel
labels.dict_stemmeroverride_button_download=Download
labels.dict_stemmeroverride_button_upload=Upload
labels.dict_stemmeroverride_file=Stemmer-Override-Datei

            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-11</id>
              <goals>
                <goal>toolchain</goal>
              </goals>
              <configuration>
                <toolchains>
                  <jdk>