Mailing-List: contact axis-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@xml.apache.org
Message-ID: <3DEE8B0F.6040606@cs.indiana.edu>
Date: Wed, 04 Dec 2002 18:09:03 -0500
From: Aleksander Slominski <aslom@cs.indiana.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.2) Gecko/20021126
MIME-Version: 1.0
To: axis-dev@xml.apache.org
Subject: Re: cvs commit: xml-axis-wsif/java/test/util WSIFTestRunner.java
References: <20021204201358.57492.qmail@icarus.apache.org>
 <01a101c29be7$d4b27110$a535ee20@55344H6>
In-Reply-To: <01a101c29be7$d4b27110$a535ee20@55344H6>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


Jeremy Hughes wrote:

>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.
>  
>
hi,

i think in this case Eclipse may have been a culprit and not CVS...

  
http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-vcm-home/docs/online/cvs_features2.0/cvs-faq.html#10_3

>This test was just to keep us honest as ^M can annoy non-windows developers.
>  
>
CVS handles automatically end of line translations so there is no need 
to fix them.

alek

-- 
The ancestor of every action is a thought. - Ralph Waldo Emerson