From user-return-46573-apmail-ant-user-archive=ant.apache.org@ant.apache.org Tue Oct 26 15:56:01 2004 Return-Path: Delivered-To: apmail-ant-user-archive@www.apache.org Received: (qmail 44310 invoked from network); 26 Oct 2004 15:56:01 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 26 Oct 2004 15:56:01 -0000 Received: (qmail 26427 invoked by uid 500); 26 Oct 2004 15:55:48 -0000 Delivered-To: apmail-ant-user-archive@ant.apache.org Received: (qmail 26379 invoked by uid 500); 26 Oct 2004 15:55:47 -0000 Mailing-List: contact user-help@ant.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Users List" Reply-To: "Ant Users List" Delivered-To: mailing list user@ant.apache.org Received: (qmail 26364 invoked by uid 99); 26 Oct 2004 15:55:47 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from [146.197.27.40] (HELO barrierb241.nike.com) (146.197.27.40) by apache.org (qpsmtpd/0.28) with ESMTP; Tue, 26 Oct 2004 08:55:45 -0700 X-Server-Uuid: F122D6CD-24F0-4253-8986-549FB7942DF9 X-MimeOLE: Produced By Microsoft Exchange V6.0.6524.0 content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: using ant to archive a file Date: Tue, 26 Oct 2004 08:54:51 -0700 Message-ID: <200410261555.i9QFthQF028669@barrierb241.nike.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: using ant to archive a file Thread-Index: AcS7T+UMxGWmd3FpQ+KbAyjHXrFBiQAI8eJQ From: "Anderson, Rob (Global Trade)" To: "Ant Users List" X-OriginalArrivalTime: 26 Oct 2004 15:54:51.0535 (UTC) FILETIME=[20DFB9F0:01C4BB74] X-WSS-ID: 6D60ACF02564391-01-01 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N I would suggest puting the config.xml into version control. Then only = keeping 1 or two backups deployed in the environment. This would allow = you to loose the DATETIMESPAMP and just rename it to config.xml.bak and = config.xml.bak.old. Then you can delete the xml.bak.old and rename the = .xml and .xml.bak with each deployment. If you need to go back more than = 2 versions, go to source control and get the one you want. -Rob Anderson > -----Original Message----- > From: Mark Lybarger [mailto:Mark.Lybarger@CBC-Companies.com] > Sent: Tuesday, October 26, 2004 4:35 AM > To: Ant Users List (E-mail) > Subject: using ant to archive a file >=20 >=20 > i'm looking for an ant task that'll do something similar to=20 > VMS's file versioning. when putting a new file out, i'd like=20 > to have the old one still there (perhaps with the ability to=20 > specify how many old versions to keep). does something like=20 > this exist?=20 >=20 > here's my specific issue: when deploying our app, we=20 > currently backup our weblogic config.xml to=20 > config.xml.bak.DATETIMESTAMP. this keeps the old config=20 > around for reference. the thing is, i only need maybe 10 or=20 > so old version laying around. this gets cluttered quickly on=20 > our cruisecontrol instance that's getting updated every hour or so. =20 >=20 >=20 --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@ant.apache.org For additional commands, e-mail: user-help@ant.apache.org