Alek,
This test was written initially to ensure none of our text files we check in
had rogue ^M characters. Agreed it's probably dangerous because it has a
side effect. Some of us use the Eclipse dev environment ... the Windows
version which has a tendancy to add ^M eg when creating a new file.
This test was just to keep us honest as ^M can annoy non-windows developers.
Jeremy
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, December 04, 2002 8:13 PM
Subject: cvs commit: xml-axis-wsif/java/test/util WSIFTestRunner.java
aslom 2002/12/04 12:13:58
Modified: java/test/util WSIFTestRunner.java
Log:
commented out FileCharacterTest as it can modify source files
replacing ^M and this is not what expected of unit tests ...
Revision Changes Path
1.24 +2 -2 xml-axis-wsif/java/test/util/WSIFTestRunner.java
Index: WSIFTestRunner.java
===================================================================
RCS file: /home/cvs/xml-axis-wsif/java/test/util/WSIFTestRunner.java,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -r1.23 -r1.24
--- WSIFTestRunner.java 4 Dec 2002 20:11:47 -0000 1.23
+++ WSIFTestRunner.java 4 Dec 2002 20:13:57 -0000 1.24
@@ -88,7 +88,7 @@
* Run JUnit tests on WSIF code.
* Add new tests to the suite() method.
* Comment out lines for tests not required.
- *
+ *
* @author Owen Burroughs
*/
@@ -106,7 +106,7 @@
// Check all files for the dreaded ^M character! If you set
// fix=on in the wsif.test.properties file, this test will
// not only check the files but also fix them.
- suite.addTest(new TestSuite(FileCharacterTest.class));
+ //suite.addTest(new TestSuite(FileCharacterTest.class));
// Test the initialisation of WSIF providers. This test needs to
be
// the FIRST of the functional tests as after this, WSIF will
already
