Paul Ramsey wrote:
On Mar 10, 2006, at 2:11 PM, Jody Garnett wrote:
I would like to format up 2.2.x when it is released, and then stick
with it (aka format before every commit like the bad old days).
Just to confirm for people, autoformatting would mean that the
workflow would be:
<workworkwork>
<build,test> <your changes work>
svn update <gets any changes since you last updated>
<build,test> <your changes work with other peoples>
svn commit <put changes into archive>
svn update <retrieve correctly formatted copy from archive>
<workworkwork>
I think a lot of people neglect that terminal svn update right now,
because it is not required.
I was thinking something slightly different paul. In our developers
guide it says that you should run Jalopy (the code formatter) before you
commit. I used to get in trouble for not doing this, now that we have
had developers pained by whitespace issues with diffs I see the errors
of my way.
<work><work><work>
<build,test> <yeah the changes work>
<format><update>
<build,test>
svn commit
<workworkwork>
So if two developers are both working on some code, they will get less
conflicts since they both format before commit.
Jody
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
