Re: Subversion help

2006-11-16 Thread Tom Chiverton
On Thursday 16 November 2006 03:30, Doug Bezona wrote: #1 - remembering to commit changed files Eclipse changes the icon of change files, as well as the filename display, if you want. #2 - remembering to copy the changed files to the server If it's a dev site, just have it do an svn update

Re: Subversion help

2006-11-16 Thread Tom Chiverton
On Wednesday 15 November 2006 20:24, Rick Root wrote: Regarding subversion, how do people handle deployment? Just copy from your local working copy to the production server, or install tortoiseSVN on the server and check out working copies there? The latter - having first copied from

OT: Subversion help

2006-11-15 Thread Rick Root
I'm finding this whole subversion thing rather complex. I haven't used source control since 1999, and I barely remember that.. I don't think it was even CVS.. it was some commercial UNIX source control package. I know that if I checked something out, it locked it on the server and others

Re: OT: Subversion help

2006-11-15 Thread Barney Boisvert
Yep, you've got it. Do a checkout from your repo into wherever you want to edit the files, edit them, and then you'll see icon decorators in Windows Explorer (from Tortoise) indicating if files are locally modified, which you should then check in. You'll want to hide/delete that stuff in d:\work

RE: Subversion help

2006-11-15 Thread Doug Bezona
Now that I've imported the files into the repository, what do I do? Do I check out the entire directory structure now so I can edit them, and then just check them in when I make changes? Yup, exactly. Since you are already using Flex builder, and now subversion, you should seriously think

Re: Subversion help

2006-11-15 Thread Rick Root
Doug Bezona wrote: Since you are already using Flex builder, and now subversion, you should seriously think about moving to cfeclipse for your CF coding as well so you can make use of the subclipse plugin from within Eclipse - it makes the whole source control thing MUCH easier to manage.

Re: Subversion help

2006-11-15 Thread Barney Boisvert
We have a dedicated staging box that is always running the same code as our production clusters. That box has a full-fledged working copy residing on it (like the dev workstations) and it used for doing final QA tests before deployment. We then use that working copy as the base for syncing up to

Re: OT: Subversion help

2006-11-15 Thread Neil Middleton
http://svnbook.red-bean.com/ Well worth a (skim) read. On 11/15/06, Rick Root [EMAIL PROTECTED] wrote: I'm finding this whole subversion thing rather complex. I haven't used source control since 1999, and I barely remember that.. I don't think it was even CVS.. it was some commercial UNIX

RE: Subversion help

2006-11-15 Thread Doug Bezona
Regarding subversion, how do people handle deployment? Just copy from your local working copy to the production server, or install tortoiseSVN on the server and check out working copies there? rick I use Ant for this - basically create an Ant task to check out a copy from SVN into a

Re: Subversion help

2006-11-15 Thread Rob Wilkerson
On 11/15/06, Rick Root [EMAIL PROTECTED] wrote: Regarding subversion, how do people handle deployment? Just copy from your local working copy to the production server, or install tortoiseSVN on the server and check out working copies there? Because I create a product, I have an ant script

Re: Subversion help

2006-11-15 Thread Rick Root
Doug Bezona wrote: I use Ant for this - basically create an Ant task to check out a copy from SVN into a temp directory and copy it the destination directory (or FTP or however you need to get the code from one place to another). And actually, if you keep the temp directory around, you can

RE: Subversion help

2006-11-15 Thread Doug Bezona
to the server. -Original Message- From: Rick Root [EMAIL PROTECTED] To: CF-Talk cf-talk@houseoffusion.com Sent: 11/15/06 7:56 PM Subject: Re: Subversion help Doug Bezona wrote: I use Ant for this - basically create an Ant task to check out a copy from SVN into a temp directory and copy