Return-Path: Delivered-To: apmail-jakarta-ant-user-archive@apache.org Received: (qmail 16554 invoked from network); 25 Sep 2002 18:35:50 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 25 Sep 2002 18:35:50 -0000 Received: (qmail 12720 invoked by uid 97); 25 Sep 2002 18:28:08 -0000 Delivered-To: qmlist-jakarta-archive-ant-user@jakarta.apache.org Received: (qmail 12503 invoked by uid 97); 25 Sep 2002 18:28:06 -0000 Mailing-List: contact ant-user-help@jakarta.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 ant-user@jakarta.apache.org Received: (qmail 12340 invoked by uid 98); 25 Sep 2002 18:28:04 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Date: Wed, 25 Sep 2002 11:27:12 -0700 From: "Paul D. Schmidt" To: ant-user@jakarta.apache.org Subject: How do people keep track of version information? Message-ID: <20020925182712.GA26101@uberhacker.org> Mail-Followup-To: ant-user@jakarta.apache.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hello, I'm looking for some advice on how people use ant + perforce to keep track of their labels, version info, etc. First of all, I'm a bit confused as to why the propertyfile task sets the properties BEFORE performing its operations and writing out the file. This puts what gets used during the build and the proeprty file that gets labelled/tagged in differing states... We need to keep track of the build number in a proprety file which can be used by the build system to substitute it into certain files that our application uses. This part seems to be fine. I'm wondering what other people (preferably who use perforce, but CVS, etc might carry over here as well) do to automatically formulate the label name, etc. Hard coding a prefix and appending the buildnumber to it works in the simplest case, but as soon as you introduce branching (which in perforce isn't metadata like in CVS, it actually puts all the files in a different location (//depot/branches/branch_name in our case), so the view= attribute, etc needs to be correct for the p4 ant tasks... Having a hard-coded build.view property set to something like "build.view=branches_pds-dev4" might work, if there's an easy way to replace _ with / from within ant (I forget, I'll have to look through the manual again). However, this would cause lots of pain for our developers, who are all on separate branches, having to merge the version.properties file (well, ignore that file every time they try to integrate actually, as their version.properties would have a different build.view in there as the mainline) Just wondering what other people do so I can get some ideas... Thanks, -Paul -- [Paul D. Schmidt...........][..........pds@uberhacker.org] [Xtime, Inc................][........http://www.xtime.com] -- To unsubscribe, e-mail: For additional commands, e-mail: