Return-Path: 
 <ant-user-return-12766-apmail-jakarta-ant-user-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-ant-user-archive@jakarta.apache.org
Received: (qmail 76552 invoked by uid 500); 20 Sep 2001 17:17:51 -0000
Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Post: <mailto:ant-user@jakarta.apache.org>
List-Help: <mailto:ant-user-help@jakarta.apache.org>
List-Unsubscribe: <mailto:ant-user-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:ant-user-subscribe@jakarta.apache.org>
Reply-To: ant-user@jakarta.apache.org
Delivered-To: mailing list ant-user@jakarta.apache.org
Received: (qmail 76542 invoked from network); 20 Sep 2001 17:17:50 -0000
Message-ID: <20010920171752.98692.qmail@web13407.mail.yahoo.com>
Date: Thu, 20 Sep 2001 10:17:52 -0700 (PDT)
From: Diane Holt <holtdl@yahoo.com>
Subject: Re: suggestions
To: ant-user@jakarta.apache.org
In-Reply-To: <1001003610.15034.58.camel@jigra.begeek.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

--- Craig Longman <craigl@begeek.com> wrote:
> 1) it seems like some way of quickly comparing a property to some value
> would be helpful.  as an '=' is almost certainly never going to be a
> valid character in a property, this kind of thing should work pretty
> well:
>   <target name="target" if="some.property=hello"/>
>   <target name="target" if="some.property=goodbye"/>

Diligently (very very :) asked for a looong time ago, and turned down
flat. (I ended up having a modified Target.java for quite awhile for that
very reason. With the advent of <condition> in 1.4, that can finally
[yay!] go away.)

> 2) something that calls one or more targets AFTER a target has
> completed.  for example, in my init target, i often have properties that
> i need to conditionally set, and currently the only way to easily do
> that is multiple targets with 'if' attributes.  but, i would still want
> to ensure that the init is completed first, while still ensuring that
> the other conditional-inits are completed immediately following the init
> target.

Maybe I'm just not fully awake yet this morning, but -- you lost me. The
only I know of to start another target before the first one is done is to
include an <antcall>/<ant> in it, then have additional tasks after that.
Eg:
  <target name="foo">
    <echo message="I'm foo..."/>
    <antcall target="bar"/>
    <echo message="I'm foo again."/>
  </target>
  <target name="bar">
    <echo message="I'm bar..."/>
  </target>

BTW: There's a problem with logging on this -- the "[echo] I'm foo again."
ends up printing out as a task of target bar (oops).

> 3) some way to silence a target.

Use NoBannerLogger.

> 4) some way to indicate that a target is to be only called from the
> build file itself, not externally.  this is basically what i'm trying to
> simulate in 3), but being able to code it directly in the build file
> might be helpful.

I suppose an attribute could be added to <target> (eg., "external";
defaults to yes), but I'm not knowledgeable enuf with Ant's internals to
say for sure how easy that would be to do.

Diane

=====
(holtdl@yahoo.com)



__________________________________________________
Terrorist Attacks on U.S. - How can you help?
Donate cash, emergency relief information
http://dailynews.yahoo.com/fc/US/Emergency_Information/