From cac8d63543a9b0379551d50b3db531279f363ac3 Mon Sep 17 00:00:00 2001 From: "Torne (Richard Coles)" Date: Tue, 13 Oct 2020 15:27:05 -0400 Subject: [PATCH] Remove incorrect statement from Log docs. The javadoc for Log stated that verbose logs are not compiled into apps and debug logs are stripped at runtime, but this doesn't happen automatically and is up to the app's Proguard/R8 configuration and/or explicit use of isLoggable. Just remove this. Fixes: 27286343 Test: m offline-sdk-docs Change-Id: I0376b20e5c324f422a5fff0201f144e447d8eac2 --- core/java/android/util/Log.java | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/core/java/android/util/Log.java b/core/java/android/util/Log.java index 7a117f14d9b5d..12bcd8b0aa977 100644 --- a/core/java/android/util/Log.java +++ b/core/java/android/util/Log.java @@ -44,9 +44,7 @@ import java.net.UnknownHostException; * You can then view the logs in logcat. * *

The order in terms of verbosity, from least to most is - * ERROR, WARN, INFO, DEBUG, VERBOSE. Verbose should never be compiled - * into an application except during development. Debug logs are compiled - * in but stripped at runtime. Error, warning and info logs are always kept. + * ERROR, WARN, INFO, DEBUG, VERBOSE. * *

Tip: A good convention is to declare a TAG constant * in your class: