Ok, we found it, ant.home=C:\apache-ant-1.6.5\, the ending \ was the problem...
thanks everybody
On 7/26/06, Conor MacNeill <[EMAIL PROTECTED]> wrote:
Do you have a CLASSPATH set? Does it have quotes in it? If so, remove
them. If you want to debug this, turn echo on in the ant.bat file and
see
Do you have a CLASSPATH set? Does it have quotes in it? If so, remove
them. If you want to debug this, turn echo on in the ant.bat file and
see what is going wrong.
Conor
jm wrote:
> Hi,
>
> we are experiencing an strange problem, never seen that before. Our
> env is ant1.6.5, jdk1.5.0.07, on a
thanks guys,
yes, we have ANT_OPTS, but not ANT_ARGS. Our scripts are working fine
in a number of machines. Now that I think the only new thing is java
1.5.0.07, it's the first time we use that update.
On 7/26/06, Burgess, Benjamin <[EMAIL PROTECTED]> wrote:
There was a bug with the Launcher cl
There was a bug with the Launcher class that was released with Ant 1.6.5
- do you by chance have any ANT_ARGS set, such as -lib or -noclasspath
etc...?
See http://issues.apache.org/bugzilla/show_bug.cgi?id=36171
Ben
-Original Message-
From: jm [mailto:[EMAIL PROTECTED]
Sent: Wednesday,
Any ANT_OPTS or ANT_ARGS vars?
Do a set ANT at the prompt to see which vars are set. --DD
On 7/26/06, jm <[EMAIL PROTECTED]> wrote:
Hi,
we are experiencing an strange problem, never seen that before. Our
env is ant1.6.5, jdk1.5.0.07, on a xp. ANT_HOME and JAVA_HOME are set
properly, ant\bin is