----- Original Message -----
From: "Peter Donald" <[EMAIL PROTECTED]>
To: "Ant Developers List" <[EMAIL PROTECTED]>
Sent: Saturday, February 23, 2002 9:06 PM
Subject: Re: <ant>
> On Sun, 24 Feb 2002 15:33, Steve Loughran wrote:
> > > -1
> > >
> > > I know people who use it with antcalls as a fallback. At one stage
some
> > > of the Avalon build files also used it. I think it is an ugly hack but
> > > unfortunately it is here to stay now ;(
> >
> > oh I see, so they can use it as an explicit default. Ugly. ugly ugly.
Why
> > is avalon always on the cutting edge of build file abuse :-)
>
> I prefer to think of it as pushing the bounds of the technology bubble ;)
Spend too much time living on the edge, eventually you fall off :)
in fact the basic rule of winter mountaineering is that if you can see the
edge you are too close, as cruft buildup (in this case snow) makes the edge
seem further away than it really is.
>
> > How do you propose we specify in ant 1.x that the target attribute of
the
> > <ant> task should refer to the default of the project?
>
> Not sure. All my build files contain a target named "main" that is always
the
> default target so I always specify that as property value prior to antcall
if
> I want that behaviour.
I'd like a target name which means default, but with "" in use, they are all
taken. Except probably comma, and that is wrong.
>
> > Presumably these targets were added so that if you invoked the build
file
> > with the target attribute bound to an empty property, the "" target was
> > executed instead. I am proposing formalising that with an invocation of
the
> > empty target mapping to calling default.
>
> unfortunately thats different from current behaviour. The "" actually was
> used to do something different. In a few cases that I am aware of its use,
> the purpose was to display a message saying "You forgot to set the
property
> you ninny!". In other cases it had different behaviour from the main
target.
ok, but
>
> > > > for a target. I think not, if we agree then we can stop it, and then
I
> > > > could set <ant target=""> to mean default.
> > >
> > > definetly for ant2.
> >
> > well in that case ant1.x should issue a warning whenever a build file
> > target of a tenuous name ("", "," ...) is declared, cos it is unlikely
that
> > they will work in ant2,
>
> +1
will file an RFE when bugzilla returns
actually, when I implement it, I could have it hit a URL to log the use of
the invalid data type, feed up the project name, then we could build a list
of who was pushing the envelope a bit too much. Course it'd be a blatant
violation of all known privacy rules, but that is a minor detail.
On a completely unrelated note, I was debating whether to add a -nice flag
to drop/raise Ant's thread priority in an x-platform manner. I have a
niceant.bat which sort of does this as a one of, and there is nice on unix
anyway, but what about the other boxes. Is there pent up user need for this?
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
