ROTECTED]>
To: "Ant Users List" <[EMAIL PROTECTED]>
Sent: Thursday, November 29, 2001 2:33 PM
Subject: Re: Scope of a property
> --- Erik Hatcher <[EMAIL PROTECTED]> wrote:
> > > For example,
> > >
> > >
> > >
> > >
> >
--- Erik Hatcher <[EMAIL PROTECTED]> wrote:
> > For example,
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > the above echo will not display any.
> >
>
> These two targets are never executed at the same time. You'd run these
> by doing one of:
>
> ant myInit showMe
>
> -or-
>
> ant myIn
> I want to discuss a little bit more on this.
A topic dear to my heart
> >From what I understand, a property within a target will not be available
to
> another target unless there is a dependence.
Well, sort of. For the same execution thread (terminology is a bit off
here) properties are
But anyway, in order to make a property global, you have to put it outside
targets.
Am I right?
thanks,
Jerry
-Original Message-
From: Stefan Bodewig [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 28, 2001 4:20 AM
To: [EMAIL PROTECTED]
Subject: Re: Scope of a property
On Wed, 28
On Wed, 28 Nov 2001, Holger Danske <[EMAIL PROTECTED]> wrote:
>
>
this is going to result in in BuildException in Ant 1.5 as one of
value,ref or location is required when using the name attribute. I'm
not sure whether this simply has been a no-op in Ant 1.4, but I think
so. So you prob
> is this literally taken from your buildfile? What
> do you expect that
> property task to do without either a value, location
> or ref attribute?
...
...
...
...
The check target is running thr
On Wed, 28 Nov 2001, Holger Danske <[EMAIL PROTECTED]> wrote:
> Many targets depends on this check target. But it is
> only once necessary to run the check target.
If a target appears more than once in the dependency graph, Ant will
still only execute it once - so it should already do what you w
