Don't set timezone explicitly to UTC
The maven master sets the timezone only for the surefire and failsafe
plugins. When a user adds other plugins like cargo he'd need to remember
adding this timezone as well to avoid hard-to-diagnose errors.
It is simpler to use the hosts timezone here so that all plugins have a
consistent setting without user configuration.
Change-Id: Ibf4f924ce56a7cdd162ac644a0a28818ae44c730
diff --git a/maven_plugin_config-master/pom.xml b/maven_plugin_config-master/pom.xml
index 1cc7904..a77e2f5 100644
--- a/maven_plugin_config-master/pom.xml
+++ b/maven_plugin_config-master/pom.xml
@@ -139,7 +139,6 @@
<argLine>${master_test_argLine}</argLine>
<systemPropertyVariables>
<sun.jnu.encoding>${project.build.sourceEncoding}</sun.jnu.encoding>
- <user.timezone>UTC</user.timezone>
<java.awt.headless>true</java.awt.headless>
<java.util.logging.SimpleFormatter.format>%1$tY-%1$tm-%1$td %1$tH:%1$tM:%1$tS %4$s %5$s%6$s%n</java.util.logging.SimpleFormatter.format>
<!-- Inherit proxy settings of parent process when forking -->
@@ -171,7 +170,6 @@
<argLine>${master_test_argLine}</argLine>
<systemPropertyVariables>
<sun.jnu.encoding>${project.build.sourceEncoding}</sun.jnu.encoding>
- <user.timezone>UTC</user.timezone>
<java.awt.headless>true</java.awt.headless>
<java.util.logging.SimpleFormatter.format>%1$tY-%1$tm-%1$td %1$tH:%1$tM:%1$tS %4$s %5$s%6$s%n</java.util.logging.SimpleFormatter.format>
</systemPropertyVariables>