ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "DoNOTuseREPLY" <>
Subject Re: ant - setup/msdos
Date Wed, 05 Feb 2003 02:07:05 GMT
The next time you run ant and get the "bad command or file name" use the
"set" command to validate ANT_HOME actually contains the correct path
information.  Also, take a look at your PATH before you run autoexec.bat.
PATH should have %ANT_HOME%\bin.  Since we are not allowed to diddle with
startup files (e.g., autoexec.bat), I use the following .bat file, at the
beginning of my ant session, to fix the session issue here at our location:

rem AntSetUp.bat 20030121 h:\Ant
@echo off

rem ** 20030120 **

set SystemDrive=h:

set ANT_HOME=%SystemDrive%\ant

set JAVA_HOME=%SystemDrive%\jdk1.4


set PATH=%PATH%;%ANT_HOME%\bin

rem ** 20030120 **

As an after thought, if you are allowed to mess with startup files at your
location and at client sites, then you may want to include the appropriate
parts of the above in the autoexec.bat.


----- Original Message -----
From: <>
To: <>
Sent: Tuesday, February 04, 2003 4:06 PM
Subject: ant - setup/msdos

> I have MicroSoft ME system
> The problem that I have using ant is:
> I have to run autoexec.bat in MSDOS everytime before I can use ant.
> I update the autoexec.bat and increased environment space to 4096.
> When in MSDOS:
> c:\>ant -version
> Bad command or file name.
> c:\>autoexec.bat
> c:\>ant -version
> Apache Ant version 1.5.1 compiled on October 2 2002
> After this, ant works fine. But when I exit MSDOS and go back in again, I
> to do the above steps again before I can use ANT.
> Why do I have to run autoexec.bat everytime? How could I fix it?
> Thank You!!!
> Wei
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

View raw message