ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From starkc <>
Subject Re: ant unable to find build.xml in another directory?
Date Fri, 10 Jul 2009 18:28:43 GMT

ddevienne wrote:
> On Fri, Jul 10, 2009 at 10:31 AM, starkc<> wrote:
>> Here is the resulting log when running that new command with the -verbose
>> flag.  I dont believe I missed anything...
>> maint:
>>     [exec] Current OS is Windows XP
>>     [exec] Executing 'cmd' with arguments:
>>     [exec] '/c'
>>     [exec] 'ant.bat'
>>     [exec] 'ejb'
>>     [exec]
>>     [exec] The ' characters around the executable and arguments are
>>     [exec] not part of the command.
>>     [exec] Buildfile: build.xml does not exist!
>>     [exec] Build failed
> It doesn't say in which directory it executes the command. I thought
> it did, strange.
> The error message indicates to me the sub-process's current directory
> is not what
> it should be, although I'm not sure as to why.
> Work-around it using a command line like "cmd /c cd /d absdir && ..."
> (basically what
> WinNTCommandLauncher does in the latest code), or by adding an explicit
> build
> file arg with an absolute path (see
> and -f)
> You may also want to play with the vmlauncher attribute. --DD
> PS: Use <property location> to generate absolute filenames.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Using "-f [path-to-buildfile]" worked, but it seems like there should be a
way for me to do this without resorting to absolute paths.  Shouldn't this
be somewhat portable?

My main concern is that everyone else on my team has this working just the
way it is, and I do not.  It seems like it must be a versioning issue or
environment issue, not the way the build.xml is structured...

View this message in context:
Sent from the Ant - Users mailing list archive at

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message