ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yves Martin <yves.mar...@elca.ch>
Subject Re: Configuring a custom task
Date Tue, 29 Mar 2005 12:32:24 GMT
Upayavira <uv@odoko.co.uk> writes:

> 1) Every time I use my task, I have to pass the task the classpath
> definition, as the task needs to create a new classloader with which to run
> my application. Is there a way to remove the necessity to mention the
> classpath, deriving it from the one used within the <taskdef>?

 I know only one: put your jar with the compiled class and a antlib.xml
 resource (or a property file) in the ANT_HOME/lib directory.

> 2) The application that the task is invoking requires a system property to be
> set. So my task takes in a property 'config', and sets the system property
> before invoking the application. But again, this needs to be done every
> time. Is there (a) a way to set a system property once that will effect all
> tasks or (b) would someone recommend a specific way to provide this
> configuration just once, e.g. set a property, and have the task always look
> for a property of that name. Is there a convention here?

 I'm not sure to have well understand your idea but you may move your 'propery'
 task out of the target - so it is common to all targets.

-- 
Yves Martin


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org


Mime
View raw message