Re: Please test Ant 1.10.16 release candidate

"Richard A. Mead" <[email protected]> Mon, 9 Feb 2026 13:34:16 -0800
Newsgroups gmane.comp.jakarta.ant.user
Message-ID <[email protected]>
I think I had 1.10.14 working previously...  and I started out with no 
quotes.   Note that java is working for me while JAVA_HOME has quotes.

Nevertheless, I remove the quotes and voila!  It is working now...

Well, ant.bat is working.  ant.cmd and antenv still return this error:

C:\Users\Richa>antenv

C:\Users\Richa>/*
'/*' is not recognized as an internal or external command,
operable program or batch file.

-Richard


On 2/9/2026 12:46 PM, Stefan Bodewig wrote:
> On 2026-02-09, Richard A. Mead wrote:
>
>> Odd - ant.bat (and thus, "ant" without an extension) is giving me this:
>> C:\>ant.bat
>> Files\Ant was unexpected at this time.
>> C:\>antenv
> I don't believe this is related to a change in Ant 1.10.16. I see the
> something similar with
>
> C:\Users\bodewig\ant>set JAVA_HOME="c:\Program Files\Eclipse Adoptium\jdk-21.0.10.7-hotspot"
>
> C:\Users\bodewig\ant>dist\bin\ant
> Files\Eclipse was unexpected at this time.
>
> This is the same with ant.bat of 1.10.15 so likely something that has
> changed prior to 1.10.15.
>
> If I remove the quotes, i.e.
>
> set JAVA_HOME=c:\Program Files\Eclipse Adoptium\jdk-21.0.10.7-hotspot
>
> it works.
>
> I'm not much of a batch file programmer myself and don't really know
> whether environment variables are expected to be quote here.
>
>> C:\>echo %ANT_HOME%
>> "C:\Program Files\Ant 1.10.16"
> Could you please try with
>
> set ANT_HOME=C:\Program Files\Ant 1.10.16
>
> instead?
>
> We can try to figure out what causes the regression by going backwards
> between Ant tags. Which version of Ant are you using so far?
>
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>