Return-Path: 
 <ant-user-return-23260-qmlist-jakarta-archive-ant-user=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-ant-user-archive@apache.org
Received: (qmail 1442 invoked from network); 25 Jul 2002 18:16:29 -0000
Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131)
  by daedalus.apache.org with SMTP; 25 Jul 2002 18:16:29 -0000
Received: (qmail 18353 invoked by uid 97); 25 Jul 2002 18:16:36 -0000
Delivered-To: qmlist-jakarta-archive-ant-user@jakarta.apache.org
Received: (qmail 18282 invoked by uid 97); 25 Jul 2002 18:16:36 -0000
Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:ant-user-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:ant-user-subscribe@jakarta.apache.org>
List-Help: <mailto:ant-user-help@jakarta.apache.org>
List-Post: <mailto:ant-user@jakarta.apache.org>
List-Id: "Ant Users List" <ant-user.jakarta.apache.org>
Reply-To: "Ant Users List" <ant-user@jakarta.apache.org>
Delivered-To: mailing list ant-user@jakarta.apache.org
Received: (qmail 18231 invoked by uid 98); 25 Jul 2002 18:16:35 -0000
X-Antivirus: nagoya (v4198 created Apr 24 2002)
Message-ID: <D44A54C298394F4E967EC8538B1E00F13D422D@lgchexch002.lgc.com>
From: Dominique Devienne <DDevienne@lgc.com>
To: "'Ant Users List'" <ant-user@jakarta.apache.org>
Subject: RE: Inventory
Date: Thu, 25 Jul 2002 13:16:12 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

I don't generate a checksum, but when doing a distrib, I generate some sort
of manifest of all the files under CVS control (which of course should
comprise all files necessary to build the app) using the following target
below.

Not that great and also might expose more to the client that he/she should
see in general, but useful to know exactly what went in the distrib. Of
course, one can tag the CVS tree as well, but we only do so for important
distribs, so this mechanism allows knowing exactly what went into every
distrib generated.

If anyone has a better idea to do that, I'd like to know too. --DD

  <!-- ====================================================
       Creates manifest listing all version of the MoWI files
     used to generate a distrib.
    -->
  <target name="cvs-manifests"
          depends="init"
          unless="no-cvs-manifests">

    <property name="mowi-cvs-manifest"
            value="${distrib}\docs\WebHelp\MoWI-CVS-Manifest.txt" />

    <cvs command="-z3 status"
         cvsRoot="${mowi.cvsroot}"
         output="${mowi-cvs-manifest}"
         quiet="${cvs-quiet}" />

    <echo file="${mowi-cvs-manifest}"
        message="Build Machine:    ${env.COMPUTERNAME}${nl}"
        append="yes" />
    <echo file="${mowi-cvs-manifest}"
        message="Base Directory:   ${basedir}${nl}"
        append="yes" />
    <echo file="${mowi-cvs-manifest}"
        message="Start time:       ${TIME_NOW} on ${TODAY}${nl}"
        append="yes" />
    <echo file="${mowi-cvs-manifest}"
        message="Java VM Version:  ${java.vm.version}${nl}"
        append="yes" />

  </target><!-- cvs~manifests -->

-----Original Message-----
From: Matt Lyon [mailto:matt@stargus.com] 
Sent: Thursday, July 25, 2002 12:20 PM
To: Ant-User (E-mail)
Subject: Inventory

Hi,

Is anybody aware of an Ant task floating around to produce an inventory or
manifest of files that are being built and included in a given project? I
have been tasked with generating an inventory of all of the files in our
product and generating a checksum for all of the files, using some sort of
CRC solution. I was checking out Ant's <checksum> task, which seems to
provide the checksum functionality I'm after, but I'm less certain on how to
approach creation of the manifest or inventory. One approach might be to do
a find . -name * - print >> inventory.txt, but we have test code in our
source tree that I would like to exclude. I'd prefer an Ant-based solution
if possible, but I can evaluate a crc tool if necessary. Any suggestion
would be greatly appreciated!

Thanks,

Matt

--
To unsubscribe, e-mail:   <mailto:ant-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-user-help@jakarta.apache.org>

--
To unsubscribe, e-mail:   <mailto:ant-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-user-help@jakarta.apache.org>