You are viewing a plain text version of this content. The canonical link for it is here.

Posted to java-dev@axis.apache.org by ow...@apache.org on 2002/10/18 13:19:20 UTC

cvs commit: xml-axis-wsif/java/test/util FileCharacterTest.java

owenb       2002/10/18 04:19:20

  Modified:    java/test/util FileCharacterTest.java
  Log:
  Added a more informative Javadoc comment
  
  Revision  Changes    Path
  1.2       +7 -3      xml-axis-wsif/java/test/util/FileCharacterTest.java
  
  Index: FileCharacterTest.java
  ===================================================================
  RCS file: /home/cvs/xml-axis-wsif/java/test/util/FileCharacterTest.java,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- FileCharacterTest.java	6 Jun 2002 08:29:00 -0000	1.1
  +++ FileCharacterTest.java	18 Oct 2002 11:19:20 -0000	1.2
  @@ -73,9 +73,13 @@
   import junit.textui.TestRunner;
   
   /** 
  - * A JUnit test to check our files for the dreaded ^M character ;-) 
  - * Thanks go to Dave Gelder whose brilliant whichjarzip code I used 
  - * as the starting point for this. 
  + * A JUnit test to check our files for the dreaded ^M character. The test displays a list of
  + * all the WSIF files it finds that contain the character.
  + * 
  + * This test is configured by the "fix" component setting in the wsif.test.properties file.
  + * If fix is set to on, this test will attempt to remove any ^M chars it finds in the WSIF files.
  + * It is recommended that fix=on if only set if you are sure that the ^M characters are present
  + * in the server copy of the file.
    *  
    * author Owen Burroughs 
    */