274743 Some unit tests are sensitive to details of build - change defaults to not normalize tests
diff --git a/releng.wtpbuilder/scripts/build/buildutilities.xml b/releng.wtpbuilder/scripts/build/buildutilities.xml
index 5053629..05599f5 100644
--- a/releng.wtpbuilder/scripts/build/buildutilities.xml
+++ b/releng.wtpbuilder/scripts/build/buildutilities.xml
@@ -28,17 +28,23 @@
     <!-- if not otherwise set, use these default properties -->
     <property
         name="debugOptimization"
-        value="true"/>
+        value="false"/>
     <!--
-        we should always normalize ("-repack") jars. For ones which are
+        We should not always normalize ("-repack") jars by default, 
+        since in production
+        we sign the jars (which does the -repack for us) and not in production
+        we don't really care so why spend the extra time. 
+        For jars which are
         not supposed to be normalized, such as pre-existing jars, they
         need to be added to the pack.properties file (see the
         updatePackProperties task). Note: signing does the -repack when
-        we sign.
+        we sign. This can be over-ridden by the caller setting normalize to true, 
+        but there are know known cases where we want to normalize (and eventually 
+        pack) the jar files but not sign them. 
     -->
     <property
         name="normalizeJarFiles"
-        value="true"/>
+        value="false"/>
     <!--
         we'll currently pack jar files, just as part of "debugging" to
         help sanity check all is working as expected. Eventually we may
@@ -48,7 +54,7 @@
     -->
     <property
         name="packJarFiles"
-        value="true"/>
+        value="false"/>
     <!--
         Let tmp site be global. Note: we use this odd
         "tmpsite-archiveName-temp" to make sure unique directories,