Re: SVN setups

2007-11-16 Thread Dinner
On Nov 16, 2007 5:48 AM, James Smith <[EMAIL PROTECTED]> wrote: > Follow up question... > Subclipse is the answers! You are using eclipse and cfeclipse, right? :-) Really, Subclipse is an outstanding SVN interface. Maybe the best.

RE: SVN setups

2007-11-16 Thread James Smith
Follow up question... What do people use locally (windows development machines) for connecting to and synchronising with the subversion server? I have been playing with tortoise but it has a few drawbacks. 1) The version log includes every file in one big list and there seems to be no way to filt

Re: SVN setups

2007-11-14 Thread Cameron Childress
I know I am a little late to the party but I made a pretty lengthy blog post on this subject a couple of years ago... http://www.sumoc.com/blog/index.cfm/2005/9/21/Subversion-Development-Models--Local-vs-Remote-Development -Cameron James Smith wrote: > I am looking into subversion and have got

Re: SVN setups

2007-11-13 Thread Dinner
On Nov 13, 2007 3:25 AM, James Smith <[EMAIL PROTECTED]> wrote: > I am looking into subversion and have got it working etc... but I am > wondering how the group organises the development with it. We currently > have > several developers machines, one testing server and one production server > and

RE: SVN setups

2007-11-13 Thread ColdFusion
velop locally and conform to standard coding practices therefore it should work across All servers, locally, testing, and production. -Original Message- From: James Smith [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 13, 2007 5:26 AM To: CF-Community Subject: SVN setups I am looking

Re: SVN setups

2007-11-13 Thread J.J. Merrick
Jay, Yeah the second option is pretty much the way to go. I have found though that the "not working on a server" is not really an issue. Here is what we do: Dev server contains the MySQL and MsSQL dev database along with the repositories Developers have local copies of ColdFusion and check out

SVN setups

2007-11-13 Thread James Smith
I am looking into subversion and have got it working etc... but I am wondering how the group organises the development with it. We currently have several developers machines, one testing server and one production server and I can see a few options... 1) Have one set of code on the testing server