Return-Path: <Jan.Materne@rzf.fin-nrw.de>
Mailing-List: contact user-help@ant.apache.org; run by ezmlm
Delivered-To: mailing list user@ant.apache.org
Received: (qmail 65342 invoked from network); 31 Mar 2003 06:15:12 -0000
Received: from dnsinet.rzf-nrw.de (193.109.238.66)
  by daedalus.apache.org with SMTP; 31 Mar 2003 06:15:12 -0000
Received: from z011104.bk.fin.local (z011104.bk.fin.local [193.109.238.140])
	by dnsinet.rzf-nrw.de (8.12.8/8.12.8) with ESMTP id h2V6FDxk031219
	for <user@ant.apache.org>; Mon, 31 Mar 2003 08:15:13 +0200
Received: by z011104.bk.fin.local with Internet Mail Service (5.5.2653.19)
	id <HDQ4FWBK>; Mon, 31 Mar 2003 08:15:22 +0200
Message-ID: <879A5AD5DD0ED511891F0003473A9B5608FF672E@Z011004>
From: Jan.Materne@rzf.fin-nrw.de
To: user@ant.apache.org
Subject: AW: How to handle conditional capabilities?
Date: Mon, 31 Mar 2003 08:15:22 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2F74C.E91FDD70"
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

------_=_NextPart_001_01C2F74C.E91FDD70
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

You usually use different targets, call the one you want and don=B4t =
use a
flag like build.type:


<project>

    <target name=3D"clean">
        <!-- delete all dirs -->
    </target>

    <target name=3D"compile">
        <!-- compile the sources -->
    </target>

    <target name=3D"dist" depends=3D"compile">
        <!-- create the archives; classes have to be compiled =3D=3D> =
depends
-->
    </target>

</project>

So you would invoke
	ant clean
or
	ant dist
or
	ant clean dist



Jan Mat=E8rne


> -----Urspr=FCngliche Nachricht-----
> Von: Duffey, Kevin [mailto:KDuffey@marketron.com]
> Gesendet am: Sonntag, 30. M=E4rz 2003 22:48
> An: user@ant.apache.org
> Betreff: How to handle conditional capabilities?
>=20
> Hi all,
>=20
> I am using Eclipse 2.1 (just released) and Ant 1.5.1. I have=20
> like 8 build scripts, one for development, one for a clean=20
> build, one to build and package, and so forth. What I would=20
> like to do is consolidate into one build file since most of=20
> the build files are the same. I am fairly familiar with the=20
> basics of ant as I have been using it for a few years. I=20
> haven't done anything like what I want to do now. Basically,=20
> I want to be able to pass in some parameters that set=20
> properties. I may have something like:
>=20
> <property name=3D"version" value=3D"1.2"/>
> <property name=3D"build.type" value=3D"clean"/>
>=20
> What I would like to do is somehow something like:
>=20
> If (build.type =3D=3D "clearn")
> {
>   <delete all dirs>
> }
> else if (build.type =3D=3D "dev")
> {
>   <compile only changes>
> }
>=20
> the properties, the compiling of source, etc is the same for=20
> all my build files so either a single build file, or perhaps=20
> some links to how to make pretty solid build scripts for=20
> different types of builds would be very helpful.
>=20
> Thanks.
>=20
>=20
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.463 / Virus Database: 262 - Release Date: 3/17/2003
> =20
>=20
>=20
> ***********************************************************
> The information contained in this e-mail message may be=20
> confidential and  protected from disclosure. If you are=20
> not the intended recipient, any dissemination, distribution
> or copying is strictly prohibited. If you think that you=20
> have received this e-mail message in error,
> please e-mail the sender at exchangeadmins@marketron.com
> ***********************************************************
>=20
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
> For additional commands, e-mail: user-help@ant.apache.org
>=20

------_=_NextPart_001_01C2F74C.E91FDD70--