Return-Path: 
 <ant-dev-return-18736-apmail-jakarta-ant-dev-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-ant-dev-archive@jakarta.apache.org
Received: (qmail 39996 invoked by uid 500); 21 Oct 2001 14:57:42 -0000
Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ant-dev@jakarta.apache.org
list-help: <mailto:ant-dev-help@jakarta.apache.org>
list-unsubscribe: <mailto:ant-dev-unsubscribe@jakarta.apache.org>
list-post: <mailto:ant-dev@jakarta.apache.org>
Delivered-To: mailing list ant-dev@jakarta.apache.org
Received: (qmail 39987 invoked from network); 21 Oct 2001 14:57:41 -0000
Message-ID: <00c901c15a40$68857cb0$0100a8c0@jose>
From: "Jose Alberto Fernandez" <j_a_fernandez@yahoo.com>
To: <ant-dev@jakarta.apache.org>
References: <m3d73kcfow.fsf@bodewig.bost.de>
 <20011019233423.DQYR13193.mss.rdc2.nsw.optushome.com.au@there>
 <003a01c15907$140660d0$0100a8c0@jose>
 <200110210048.f9L0mvq00722@mail012.syd.optusnet.com.au>
 <007e01c15a17$a49a5550$0100a8c0@jose>
 <01a001c15a23$ed8c3ab0$6401a8c0@darden.virginia.edu>
Subject: Re: [Ant2] Tasks as siblings of <target>
Date: Sun, 21 Oct 2001 15:55:17 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.3018.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

From: "Erik Hatcher" <jakarta-ant@ehatchersolutions.com>

> Currently a <script> task could not easily accept a <fileset> as other =
tasks
> do (as embedded sub elements).  I'm sure there is some roundabout =
trickery
> that could reference a fileset defined elsewhere, but nothing that =
provides
> a pluggable framework such that <script> could cleanly take a =
<fileset> (or
> a set of filesets, attributes, etc) and get the same introspection =
mechanism
> invoked that a regular Java developed task enjoys.  I don't think I'm
> missing some wonderfully elegant way to accomplish this currently, but =
if I
> am I'd love to be enlightened as to how.
>=20
> Am I at least in the same ballpark as the ideas being discussed here?
>=20

Actually I had not gone even that far. :-) Although your point is well =
taken.
Some of the reasons why I believe the current (or proposed) =
infrastructure for
task/type declaration may be lacking when declaring other things =
(scripts, for example)
is that there may be additional information that needs to be registered =
for this other
things which is not supported by an API just registering name-class =
pairs.

Granted, the implementation class can always implement its own storage =
and
its own naming space interpretation. This is the way proposed by the =
Servlet API,
but in there you have an URL you can use as key for your naming-space.
In the case of ANT, it is a little different since we only have the name =
of the task
(unless you add some other attribute to identify the actual script). =
Then, if you want
a good integration you would like to support different namespaces in =
different
project objects (<projectref>ed or <ant*>ed) not  a fix global space, =
just as it should
be for regular tasks. I would be nice if that could be supported =
transparently.

And of course, the reason why I mentioned scripting on the first place =
was because
such a construct would in escence be performing a declaration (declaring =
the script
to be executed) as such it fits my vision of Declaring things. Can it be =
done by the
current datatypes? Maybe, but DT do not provide different structures for =
declaring it
and using it, which is what one wants with tasks defined by scripts. =
Sure we can probably
go around that some more, but when does going around becomes more =
complex than
what we want to acomplish ourselves?

Jose Alberto

>     Erik
>=20
>=20
> ----- Original Message -----
> From: "Jose Alberto Fernandez" <j_a_fernandez@yahoo.com>
> To: <ant-dev@jakarta.apache.org>
> Sent: Sunday, October 21, 2001 6:03 AM
> Subject: Re: [Ant2] Tasks as siblings of <target>
>=20
>=20
> From: "Peter Donald" <donaldp@apache.org>
>=20
> > > Define tasks using a scripting language (like javascript) and =
allow
> > > invoking such tasts simillar to regular tasks. This will definetly =
need
> > > some new datastructure to store the definition which differs from =
what
> > > regular taskdef do today.
> >
> > No it doesn't.
>=20
> Why do you think it does not? Can you be more specific?
>=20
> JA
>=20
>=20
>=20