Re: Struts Coding Standard

[Erik Hatcher]

Just as a data point to this discussion, the XDoclet project uses Pretty to do code formatting during the build process. It seems to work fine, and of course, only touches files that should be touched (the ones you're working on). Its odd sometimes to pop back to an IDE from a command-line build and see the files refresh and change slightly.

But in general this gives the code consistency and I'm pleased with how it works.

Erik


On Monday, January 6, 2003, at 04:28 PM, Craig R. McClanahan wrote:

On Mon, 6 Jan 2003, Robert Leland wrote:

I suggested before having the code
automatically formatted when a checkin or
checkout happens.

I've worked on a couple of projects that tried this, and we ultimately
gave up on it as being unsatisfactory. The problem was that the
formatting changes would obscure the functional changes, and created a lot
of "noise" in the commit diffs. You'd think this would go away after each
file has been checked out and updated at least once, but that never really
seems to happen (because the formatting rules often get tweaked).

Craig


--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>