Ok - so maybe not for idiots. Anyone that wants to use SVN for source control can't be all daft.... ;)
I've used SVN and Trac in the past with other peoples projects, but having seen Andy Allan's post on setting up Trac on windows and then listening to the guys at ColdFusion Podcast doing their schpeel on SVN I decided that it was time I sorted out my own SVN server for work.To start with I got thoroghly distracted by the big blob of yellow text on the binary packages page on the SVN site that says that the SVN client works on windows, but the server doesn't. Then I got distracted by the SVN FAQ that also says that SVN Server doesn't run on windows and talks about the Apache Portable Runtime. All this had Andy giving me weird electronic looks via google talk and asking me wtf I was talking about! All I had to do was install SVN and Apache and that was it!
I should mention that I asked Andy about SVN 1 Click Set up - his response was fairly to the point and suggested that blunt instruments would be used about my bodily-person if I used it, because it sets up SVNServe which can cause concurrency issues and Apache is better anyway.
So I resorted back to Google and came up with this article! HOWTO: Subversion for Windows with Apache server - a beginner's guide. This article is very good. It provides all the information you need to get up and running, including setting up users, permissions and backing up your projects, as well as providing a direct link to the SVN windows downloads.
I used the svn 1.3.2 setup exe and that worked fine for me.
The next task was to get my existing project into SVN. Eclipse 3.2 with subclipse didn't seem to have a means to put an existing project into a repository or at least no clear means of doing this. I've used TortoiseCVS before, so I grabbed TortoiseSVN and installed that. Annoyingly Tortoise asks you to restart at the end of installation, but you can quite happily ignore that and it'll work anyway.
TortoiseSVN attaches itself to the right-click menu providing you a bunch of SVN tools for folders and files. For a folder that isn't already associated with SVN there are only a couple of options - one of those options is "export". The export function allows you to specify an svn repository and folder and export the content to that repository. So thats exactly what I did!
I made sure I had my trunk, branches and tags folder made in my project's SVN repository, selected my existing project and then exported its content to the trunk folder.
The last thing I had to so was get eclipse to synchronise with SVN.
Under SVN Repository Explorer I added the url for the project's repository, right-clicked on the trunk folder and then selected "checkout". I was then prompted to create a new project or to select an existing project. I selected my already existing project.
Now - something slightly scary happens.... You get prompted to delete the existing project content. As long as no one has edited any of the files in your project since you put them into the repository this is fine - all your files get replaced with the exact same files from SVN.
My project is pretty small at the minute, so its not like it had to replace a vast quantity of files. You might also want to download the SVN version into a new project and move/remove the existing project yourself.
There's probably an easy way to put your eclipse project that I've completely missed without all this messing. If anyone knows, please drop me a note.
Next job is installing Trac from Andy's blog entry.