> -----Original Message----- > From: Steve Loughran [mailto:[EMAIL PROTECTED] > Dominique Devienne wrote: > >>From: Alan Brown [mailto:[EMAIL PROTECTED] > >> > >>I have a master build file in Project that uses the Ant task to call > >>targets in slave build files in the directories below it (tools, server > >>and client). One of these slave build files (Tools) uses Subant to call > >>build files dynamically in directories below it. However, in this > >>scenario the baseDirectory is not set correctly and remains as the Tools > >>directory. > >> > >>This is confirmed by the fact that all runs perfectly well if I run 'ant > >>build' directly from the Tools directory. It's only running it from > >>Project that causes the failure. > >> > >>Does anyone know a workaround to this problem? > > > > It may be a bug indeed!? > > > > But a possible work around would to not use <ant> from the master > > build, but <subant> as well, or use <ant> is such a way that you > > do not override the basedir of the Tools build. > > > > The problem might be the interaction of <ant> + <subant>. --DD > > Interesting...I've been seeing the same thing, but thought it was > something of mine, not a real bug. Now I am not so sure.
I've never seen the problem myself, but probably because I never override the basedir when using <ant>, and I made <subant> explicitly not do it. I don't think I want to investigate it too much either, 'cause I don't use it ;-) Does anybody know what's the actual use case for overriding the basedir of the sub-build called with <ant>? I've never really understood why this was possible, and always thought it to be a sticky point with most users. I steer clear of <ant>'s basedir-override mechanism myself, just to save me grief. How are people taking advantage of it? And is it worth the trouble it --DD --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
