Modifying the test so it creates a new format object rather than reusing the static one. For some reason it gives the wrong response and it's hard to see why given that it works for other methods and JUnit is single threaded. This is discussed in CLI-40

git-svn-id: https://svn.apache.org/repos/asf/jakarta/commons/proper/cli/trunk@412456 13f79535-47bb-0310-9956-ffa450edef68

Author: hen

src/test/org/apache/commons/cli2/validation/DateValidatorTest.java

@@ -65,7 +65,10 @@ public void testDefaultDateFormatValidate()
         validator.validate(list);
 
         final Iterator i = list.iterator();
-        assertEquals("2003-12-23", YYYY_MM_YY.format((Date) i.next()));
+        // CLI-40: For some reason, the YYYY_MM_YY object gets quite 
+        // confused here and returns 2003-12-22. If we make a new one 
+        // there is no problem.
+        assertEquals("2003-12-23", new SimpleDateFormat("yyyy-MM-dd").format((Date) i.next()));
         assertFalse(i.hasNext());
     }