Re: Why does the OpenSymphy build automatically run the code formatter

The trouble is you end up diffing the entire (java) fileset. Given (from 
what I know) that CVS is transferring the entire content of each file 
between you and the repo to do a diff, that's problematic when you are 
hitting a CVS server like Sourceforge, that barely has any bandwidth 
available.

Interestingly enough, this wouldn't be a problem with Subversion. It's 
built on the premise that disk space is cheap, but bandwidth is still 
pretty expensive, so it keeps around a copy of the old version on your 
system, and only sends up the actual diffs to the server.


Hani Suleiman wrote:

> Hm, I'd say the opposite is true? Running the code formatter makes 
> sure that no matter how much one changes locally, you can just 
> reformat it so that it's in the same style that is in CVS. This makes 
> diffs show up much nicer. Eg, if you add spaces or carriage returns, 
> they'll be modified. If you make local changes, then run the formatter 
> against your source tree too. That way you'll get much cleaner merges.
>
> All code checked in has been run through the formatter.
>
> On Wednesday, June 25, 2003, at 09:20 AM, Colin Sampaleanu wrote:
>
>> Sorry if this is a stupid question (i.e it has been asked before, or 
>> I am missing something), but why does the OSWorkflow build 
>> automatically run the code formatter?  This obvisoulsy makes finding 
>> out what has changed vs. CVS much harder, and forces a merge when 
>> pulling in updates.
>>
>> Regards,
>>
>> Colin
>




-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php