Hello, What fails? A task or the whole ant?
You can set the classpath in the tasks you call. -- Jürgen Knuplesch Geschäftsführer: Uwe Seltmann HRB Stuttgart 17655 USt-IdNr.: DE 811944121 -----Ursprüngliche Nachricht----- Von: merlin_the_happy_pig [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 5. September 2008 17:00 An: [email protected] Betreff: Setting classpath for nested ant call Ant newbie here. I need to call another ant task in a different build file, so I do: <project name... <target name... <ant dir= antfile= target= inheritRefs="true" inheritAll="true" ... The problem is is that this nested ant call fails because the classpath is wrong. Normally this target is called after a setenv.bat file has been called, which generates the correct classpath. I would like to do something like: <project name... <classpath> <!- add all libs needed to classpath --> <target name... <!-- inherit this correct classpath --> <ant dir= antfile= target= inheritRefs="true" inheritAll="true" I can't find a way of doing this!? -- View this message in context: http://www.nabble.com/Setting-classpath-for-nested-ant-call-tp19333163p19333163.html Sent from the Ant - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
