ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dominique Devienne <DDevie...@lgc.com>
Subject RE: [PATCH] User defined types and tasks to be loaded before defa ult ones are...
Date Tue, 26 Nov 2002 20:41:39 GMT
Fixed typos... --DD

-----Original Message-----
From: Dominique Devienne [mailto:DDevienne@lgc.com] 
Sent: Tuesday, November 26, 2002 2:40 PM
To: 'Ant Developers List'
Subject: RE: [PATCH] User defined types and tasks to be loaded before defa
ult ones are...

I'm confused by what you just wrote!

I have a custom selector impl. The only way to plug in to the selector
mechanism (which I find really great by the way) is thru the extend
selector. It's not a task. The Java class is loaded by ExtendSelector
directly if I specify a classpath, so I cannot access any tasks/types loaded
from <task/typedef>.

So how can I already have my custom selector access Project and take a
nested <path>? And how can I cast that Path into my custom Buildpath data
type, which by the way itself loads a dynamic resolver class (what I called
a custom extension point earlier).

Where you talking about what will be possible after some of [embed] make it
to Ant Core? Like I said, I'm confused... --DD

-----Original Message-----
From: Costin Manolache [mailto:cmanolache@yahoo.com] 
Sent: Tuesday, November 26, 2002 2:24 PM
To: ant-dev@jakarta.apache.org
Subject: RE: [PATCH] User defined types and tasks to be loaded before defa
ult ones are...

> I personally believe we need a mechanism to load and configure other types
> of Ant extension points (Mappers, Conditions, Selectors, Filters,
> XmlCatalog resolvers, and even custom extension points) similarly to
> what's currently possible for tasks/types, which is good enough for now.

I think we do have one already :-)

Any task can call methods in Project and core and add whatever hooks it
wants. 

For example in order to plug a particular antlib impl or a PropertyHelper
you just have a regular task that calls the add method.

It is easy to add "magic" - i.e. if a task implement one of the hooks
interfaces we can add it automatically, but it's more flexible and
clean to let the task control that ( apache2 modules follow the same
model, there is a single "module" that can add itself to any hook ).

--
To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>

--
To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>


Mime
View raw message