Dan, the answer depends on the setting of the /slide/[EMAIL PROTECTED]"auto-version-control"] in domain.xml. (ref http://jakarta.apache.org/slide/howto-deltav.html) If you have it disabled, then the only time you get a new version is when you do a checkout followed by a checkin. Note that, contrary to what happens in most version-control systems, in SLIDE locks, and checkouts and checkins, are distinct operations. i.e. locking something means no-one else can write to it. Checking out and checking it back in again means that you are going to create a new version. If you have the file locked and checked-out, you can do as many puts as you want. The most recent of these will become the new version if you do a check-in, or the state of the resource will roll back to the pre-checked-out version if you do an uncheckout. The distinct check-in/check-out model works just fine if you have a version-aware client, but if you don't you're in a bit of a bind. Enter the auto-version-control parameter. With this parameter you can tune how slide treats puts on checked-in resources. There are a number of different settings for this parameter, but the one that most people seem to use is checkout-checkin. When set to this, if you try and do a put on a non checked-out version controlled resource, SLIDE will automatically checkout the resource, and check it back in on your behalf. i.e.each time you do a put, you will get a new version (providing you have a write lock for it ;-) .
Anthony. > -----Original Message----- > From: Dan Tenenbaum [SMTP:[EMAIL PROTECTED] > Sent: Saturday, 18 March 2006 8:17 > To: [email protected] > Subject: using version control in slide > > I have been using slide for some time, with version control activated > (as it is by default). > > Now I finally want to look at the change history for some files that > are in the slide repository (they were put there with the PUT command > of the command line client). > > The jakarta slide site (and the slide-doc webapp) provide very little > information about how to use version control in slide. I am looking at > some of the DeltaV documents but they are fairly opaque (I'd always > rather look at examples than read a spec). > > Anyway, I have a couple of specific questions: > > 1) If I have been using PUT to put resources in my repository, often > overwriting previous versions of resources, is Slide putting these > resources under version control? Or do I need to do something else to > put a resource under version control? > > 2) Are all the commands I need for version control available in the > command-line client that is available with Slide? Or should I use some > other client--any recommendations? Or do I need to write code to do > this? > > 3) Does anyone know of a web page or something somewhere that explains > the version control stuff concisely and offers examples of common > operations? > > Thanks > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > ----------------------------------------------------------------------------------- This e-mail is sent by Suncorp-Metway Limited ABN 66 010 831 722 or one of its related entities "Suncorp". Suncorp may be contacted at Level 18, 36 Wickham Terrace, Brisbane or on 13 11 55 or at suncorp.com.au. The content of this e-mail is the view of the sender or stated author and does not necessarily reflect the view of Suncorp. The content, including attachments, is a confidential communication between Suncorp and the intended recipient. If you are not the intended recipient, any use, interference with, disclosure or copying of this e-mail, including attachments, is unauthorised and expressly prohibited. If you have received this e-mail in error please contact the sender immediately and delete the e-mail and any attachments from your system. If this e-mail constitutes a commercial message of a type that you no longer wish to receive please reply to this e-mail by typing Unsubscribe in the subject line. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
