No it won't. There is currently no way that I know of in Ant 1.5.1 to extend (within the build file) the ClassPath Ant uses to load its own tasks/classes, if these tasks are declared in the core or optional tasks.properties files Ant loads on startup.
The usual work around I believe involves pulling either the task name=classname reference in its defining tasks.properties file (resource when JARed up), and doing the <taskdef> with nested <classpath> manually. I don't recall if extracting the tasks classes from ant/optional.jar was also necessary. There's some more details info regarding this procedure for <junit> (might actually be a FAQ entry...). Costin and/or Conor and/or Stefan and/or Erik and/or Steve could probably give you more info, or whether what I'm saying above isn't complete rubbish. Hope that helps, --DD -----Original Message----- From: Frot [mailto:[EMAIL PROTECTED]] Sent: Monday, January 20, 2003 5:10 PM To: Ant Users List Subject: Re: <mail> Does this do the trick ?? <path id="classpath"> <fileset dir="MY_VERY_SPECIAL_NON_CLASSPATH_PATH_HERE/lib"> <include name="**/*.jar"/> </fileset> </path> Fred *********** REPLY SEPARATOR *********** On 20/01/2003 at 14:26 Nau, Michael wrote: >I don't see a classpath parameter for the mail task - is there a way for >me to add activation.jar and mail.jar to a classpath so I can use the >mail task without having to copy the files to my ant/lib dir? > >In our build environment we have everything we might need in a central >repository that our component ant scripts use to run. So for example, >all our custom tasks are packaged into a custom-tasks.jar file. Then if >a component's ant scripts needs any of these tasks it specifies that it >depends on custom-tasks.jar and it is pulled down whenever those tasks >are used. The idea being that any component can be built/manipulated >without having to install anything special (other than ant and the jdk > >I would like to do something similar for the ant task, but without it >supporting a separate classpath - I'm not sure how? > >Any ideas? > >Thanks, >Mike > > > >-- >To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> >For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
