You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by Erik Hatcher <ja...@ehatchersolutions.com> on 2002/03/03 22:14:10 UTC
Re: Two possible new tasks
Diane,
So where are these new tasks? :) I *need* them! :))
Also, are there any objections to making these tasks available outside of a
<target> so that they can used alongside <property>?
Erik
----- Original Message -----
From: "Diane Holt" <ho...@yahoo.com>
To: "Ant Developers List" <an...@jakarta.apache.org>
Sent: Thursday, February 28, 2002 4:17 AM
Subject: Re: Two possible new tasks
> --- Peter Donald <pe...@apache.org> wrote:
> > Consider the following case. Property X has the location of a dependent
> > jar and you need to create a fileset from that property.
>
> Bingo. Thanks, Pete -- I knew there had to be good reason out there
> somewhere :) That solves the age-old, "How can I specify a single
> filename to something that requires a fileset?" Now you don't need to.
>
> Diane
>
> =====
> (holtdl@yahoo.com)
>
>
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Greetings - Send FREE e-cards for every occasion!
> http://greetings.yahoo.com
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Two possible new tasks
Posted by co...@covalent.net.
On 4 Mar 2002, Stefan Bodewig wrote:
> On Sun, 3 Mar 2002, Erik Hatcher <ja...@ehatchersolutions.com>
> wrote:
>
> > Also, are there any objections to making these tasks available
> > outside of a <target> so that they can used alongside <property>?
>
> Strong objections against adding any new special cases, yes.
>
> We sort of agreed to allow *all* tasks outside of <target>s in Ant2,
> we could do so right now, if we wanted to.
+1.
This in particular would eliminate type/task ambiguity, allow us
to either make Typedef extend task or the reverse ( but have
shared code for both ). The only reason so far for separate code
is that types are allowed at top level, while most tasks are not.
Costin
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Two possible new tasks
Posted by Stefan Bodewig <bo...@apache.org>.
On Sun, 3 Mar 2002, Erik Hatcher <ja...@ehatchersolutions.com>
wrote:
> Also, are there any objections to making these tasks available
> outside of a <target> so that they can used alongside <property>?
Strong objections against adding any new special cases, yes.
We sort of agreed to allow *all* tasks outside of <target>s in Ant2,
we could do so right now, if we wanted to.
Stefsn
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Two possible new tasks
Posted by Diane Holt <ho...@yahoo.com>.
--- Erik Hatcher <ja...@ehatchersolutions.com> wrote:
> So where are these new tasks? :) I *need* them! :))
I have to find the time to write test-cases for them, and that's not
something I can just whip out, since I've never written any before -- just
added something for <available>.
In the meantime, you're welcome to just have them -- I've attached the
jar.
> Also, are there any objections to making these tasks available outside
> of a <target> so that they can used alongside <property>?
Tried that a long time ago with <available>, but it didn't fly.
Diane
=====
(holtdl@yahoo.com)
__________________________________________________
Do You Yahoo!?
Yahoo! Sports - sign up for Fantasy Baseball
http://sports.yahoo.com