Do not log legacy warnings in JUnit tests (#11963)

Change-Id: I5549a524d7fae32b1ef201073ab48cadcc4e8212

diff --git a/server/src/com/vaadin/data/util/LegacyPropertyHelper.java b/server/src/com/vaadin/data/util/LegacyPropertyHelper.java
index 3eb22524f8ddfe4ec3ea570c9c046f9847c18e84..551d7223d6c17bd8b4a721e77c7429662ce01c7b 100644 (file)
--- a/server/src/com/vaadin/data/util/LegacyPropertyHelper.java
+++ b/server/src/com/vaadin/data/util/LegacyPropertyHelper.java
@@ -77,8 +77,8 @@ public class LegacyPropertyHelper implements Serializable {
      */
     public static boolean isLegacyToStringEnabled() {
         if (VaadinService.getCurrent() == null) {
-            // This should really not happen but we need to handle it somehow.
-            // IF it happens it seems more safe to use the legacy mode and log.
+            // This will happen at least in JUnit tests. We do not what the real
+            // value should be but it seems more safe to use the legacy mode.
             return true;
         }
         return VaadinService.getCurrent().getDeploymentConfiguration()
@@ -87,9 +87,9 @@ public class LegacyPropertyHelper implements Serializable {
 
     private static boolean logLegacyToStringWarning() {
         if (VaadinService.getCurrent() == null) {
-            // This should really not happen but we need to handle it somehow.
-            // IF it happens it seems more safe to use the legacy mode and log.
-            return true;
+            // This will happen at least in JUnit tests. We do not want to spam
+            // the log with these messages in this case.
+            return false;
         }
         return VaadinService.getCurrent().getDeploymentConfiguration()
                 .getLegacyPropertyToStringMode() == LegacyProperyToStringMode.WARNING;