{"id":648,"date":"2004-12-09T19:41:44","date_gmt":"2004-12-09T23:41:44","guid":{"rendered":"http:\/\/wordpress.cephas.net\/?p=648"},"modified":"2020-05-27T09:22:01","modified_gmt":"2020-05-27T17:22:01","slug":"source-control-with-subversion-on-windows","status":"publish","type":"post","link":"https:\/\/cephas.net\/blog\/2004\/12\/09\/source-control-with-subversion-on-windows\/","title":{"rendered":"Source Control with Subversion on Windows"},"content":{"rendered":"

We’re getting around to hiring an additional me at work so I needed to get a source control solution in place before he\/she arrives and starts hacking away at the codebases. At the last place I worked we used Visual SourceSafe<\/a> for a long time (which was pretty worthless) and then started using CVS, although not on the projects I worked on. A couple weeks ago I asked a bunch of questions about automating Java web application deployment<\/a> and Erki suggested that I buy and read the Pragmatic Project Automation book<\/a>, which I did and which I loved. I read it from start to finish (which isn’t an easy thing to do with a technical book) and took a ton of notes. Anyway, I’m pretty sure the book didn’t mention Subversion<\/a> even once, but it did drill home the importance of setting up your code in source control and then doing your manual, scheduled, automated (using CruiseControl<\/a>) or production builds directly from the source control system using Ant<\/a> or Groovy<\/a>, which led to alot of ideas about how you could automate builds to production Tomcat systems. I’ve heard alot about Subversion; it’s described as CVS with none of the warts and all of the features, so I tried it out. Following are the notes I kept during the installation process. Hopefully this helps out someone somewhere down the road:<\/p>\n

a) Download Subversion<\/a> (obviously) I downloaded version 1.1.1 ( svn-1.1.1-setup-2.exe)<\/p>\n

b) Run the install. I chose to install to c:\\subversion\\.<\/p>\n

c) Test the Subversion install by going to the install directory and then going to the \/bin directory. Run the svnadmin from the command line:
\nCD c:\\subversion\\bin\\
\nsvnadmin<\/code>
\nIf you get an error that says that says “svnadmin.exe – Unable To Locate DLL”, you’ll need to either a) install the Visual C++ 6.0 VCREDIST.exe, which is available here<\/a> (but only if you’re using Windows 98 or Windows ME) or b) find someone or some system that has msvcp60.dll and copy that file to c:\\$windows\\system32\\ (where $windows is the directory that contains your Windows installation).<\/p>\n

d) Create a repository on the machine that is going to host your source code. From the command line on the server machine:
\nsvnadmin create d:\\$projects\\$projectname<\/code>
\nwhere $projects is the name of a folder that will contain all your Subversion source code repositories and $projectname is the name of the specific project you’re going to create a repository for.<\/p>\n

e) Start the server either from the command line:
\nsvnserve -d -r d:\\$projects<\/code>
\nor use the SVN Service Wrapper (http:\/\/dark.clansoft.dk\/~mbn\/svnservice\/<\/a>), note that the r<\/code> switch limits directory browsing by specifying the root of your repositories.<\/p>\n

f) Create a users database (which is nothing more than a text file, I created a file called users.conf) and save it in the d:\\$projects\\$projectname\\conf<\/code> directory and then add your usernames & passwords. An example user database might look like this:[users]
\naaron = mypassword<\/code><\/p>\n

g) Within the d:\\$projects\\$projectname\\<\/code>directory, open the conf\/svnserve.conf file using your text editor of choice and add the following to allow reading and writing to the users in the database we just created:
\n[general]
\nanon-access = none
\nauth-access = write
\npassword-db = users.conf
\nrealm = $projectname
\n<\/code>
\nwhere $projectname is the name of the project you’re setting up and users.conf is the name of the file you created in step f.<\/p>\n

h) Finally, restart the server and you’re ready to start using the client and import your project.<\/p>\n

i) To import an existing project, invoke the svn executable from the command line on the client:
\nsvn import c:\\temp\\myproject svn:\/\/myserver\/myproject -m \"initial import\" aaron mypassword
\n<\/code>
\nwhere c:\\temp\\myproject<\/code> is the directory that contains the existing project you want to import (and should have 3 folders: trunk, tags and branches, your source code should be in the trunk folder; more on repository layout here<\/a>), myserver<\/code> is the name of the server that contains the Subversion repository you created in step d, myproject<\/code> is the name of the project (ie: $projectname from step d) you’re importing into, the m<\/code> switch signifies the message you want to tag this import with, followed by the username and password you setup in the users database in step f.<\/p>\n

j) Finally, checkout the project from the server (invoking the svn executable from the directory that you want the trunk checked out from…, ie: c:\\projects\\myproject<\/code>)
\nsvn co svn:\/\/myserver\/myproject\/trunk . aaron mypassword
\n<\/code><\/p>\n

k) To add, move, delete, or edit and then commit any changes back to subversion:
\nAdd: svn add src\/myfile.java -m \"adding a file\"<\/code>
\nMove: svn move src\/myfile.java src\/mynewfile.java -m \"moved myfile.java to mynewfile.java\"<\/code>
\nDelete: svn delete src\/myfile.java -m \"removing a file\"<\/code>
\nCommit: svn commit src\/myfile.java -m \"the message\"<\/code><\/p>\n

That’s it… there’s a alot more to read. One of the coolest things about Subversion is that the documentation is all packaged up into a free PDF published by Oreilly, which you can download here<\/a>. I printed out the manual and breezed through it in a couple hours. You should too.<\/p>\n

I did try to get the Subclipse Eclipse Subversion plugin<\/a> working, but for the life of me… I couldn’t. I think it ended up for the better anyhow because while the command line is a bit more tedious, I understand more about what’s going on in the system, which is helpful. I’d recommend that you get familiar with the command line client before attempting to use a GUI plugin.<\/p>\n

After you’re all set with Subversion and you’re ready to get started with CruiseControl, note that while Cruisecontrol contains an <svn><\/code> tag, you still need to drop down into command line mode in Ant to checkout \/ update your local repository when doing an automated build. For example:
\n<exec executable=\"svn\">
\n  <arg line=\"update\"\/>
\n<\/exec><\/code><\/p>\n","protected":false},"excerpt":{"rendered":"

We’re getting around to hiring an additional me at work so I needed to get a source control solution in place before he\/she arrives and starts hacking away at the codebases. At the last place I worked we used Visual SourceSafe for a long time (which was pretty worthless) and then started using CVS, although … Continue reading Source Control with Subversion on Windows<\/span> →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[3,4,2,12],"tags":[],"_links":{"self":[{"href":"https:\/\/cephas.net\/blog\/wp-json\/wp\/v2\/posts\/648"}],"collection":[{"href":"https:\/\/cephas.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cephas.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cephas.net\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/cephas.net\/blog\/wp-json\/wp\/v2\/comments?post=648"}],"version-history":[{"count":3,"href":"https:\/\/cephas.net\/blog\/wp-json\/wp\/v2\/posts\/648\/revisions"}],"predecessor-version":[{"id":3059,"href":"https:\/\/cephas.net\/blog\/wp-json\/wp\/v2\/posts\/648\/revisions\/3059"}],"wp:attachment":[{"href":"https:\/\/cephas.net\/blog\/wp-json\/wp\/v2\/media?parent=648"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cephas.net\/blog\/wp-json\/wp\/v2\/categories?post=648"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cephas.net\/blog\/wp-json\/wp\/v2\/tags?post=648"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}