String url = new DocumentationRegistry().getDocumentationRecommendationFor("information on how to set these values", "build_environment", "sec:configuring_jvm_memory");

            logger.warn(EXPIRE_DAEMON_MESSAGE + when + " " + reason + ".\n"

== OTHER TOPICS

include::directory_layout.adoc[leveloffset=+2]
include::working_with_files.adoc[leveloffset=+2]
include::logging.adoc[leveloffset=+2]
include::potential_traps.adoc[leveloffset=+2]
include::build_environment.adoc[leveloffset=+2]
include::init_scripts.adoc[leveloffset=+2]
include::custom_gradle_types.adoc[leveloffset=+2]
include::build_services.adoc[leveloffset=+2]
include::dataflow_actions.adoc[leveloffset=+2]

include::sample[dir="snippets/maven-publish/javaProject/groovy",files="build.gradle[tags=repo-url-from-variable]"]
====

Similarly, you can use a <<build_environment.adoc#build_environment, project or system property>> to decide which repository to publish to. The following example uses the release repository if the project property `release` is set, such as when a user runs `gradle -Prelease publish`:

                    "%s",
                getConfidenceNote(sslException),
                join(", ", supportedTlsVersions),
                documentationRegistry.getDocumentationRecommendationFor("on this", "build_environment", "sec:gradle_system_properties")
            );
        }
        return new HttpRequestException(message, e);
    }

    @Nonnull

* a `gradle.properties` file in the `$HOME/.gradle` directory

Those aren't the only options, so if you are interested in finding out more about how and where you can define properties, check out the <<build_environment#build_environment,Build Environment>> chapter.

image::plugin-portal-api-keys.png[]

It is common practice to copy and paste the text into your <<build_environment.adoc#sec:gradle_configuration_properties,$HOME/.gradle/gradle.properties>> file, but you can also place it in any other valid location.

`gradlew`, `gradlew.bat`::
A shell script and a Windows batch script for executing the build with the Wrapper.

== Choosing a log level

You can choose different log levels from the command line switches shown in <<#logLevelCommandLineOptions, Log level command-line options>>.

You can also configure the log level using <<build_environment.adoc#sec:gradle_configuration_properties,`gradle.properties`>>.

In <<#stacktraces,Stacktrace command-line options>> you can find the command line switches which affect stacktrace logging.

[[logLevelCommandLineOptions]]

This chapter has covered the major topics that are specific to migrating Ant builds to Gradle.
All that remain are a few other areas that may be useful following a migration:

 * Learn how to configure Gradle's <<build_environment#build_environment,build environment>>, including the JVM settings used to run it
 * Learn how to <<organizing_gradle_projects#organizing_gradle_projects,structure your builds effectively>>

If your server's certificate is not trusted, you can:

1. Update the trust store of your Java runtime to allow it to be trusted
2. Change the <<build_environment.adoc#build_environment,build environment>> to use an alternative trust store for the build runtime
3. Disable the requirement for a trusted certificate