Here's an extract of a .bat script where we had the same problem. A Java
system property had a quoted path ending in a back-slash, and apparently
java.exe chokes on it. I've solved the issue by escaping the back-slash when
finding a {back-slash, double-quote} sequence of character. See below.And yes, even with cmd.exe there's a limitation in the DOS command line. Had too many jars in classpath, and too many Java system properties on the java.exe command line. Either merge your jars, or state JAR dependencies in the Class-Path attribute of your JAR manifests to turn around them, or use another script language (PERL, PYTHON, etc...), but then you have to distrib it with your app to start it up. Or write your own startMyApp.exe... --DD :: replace all the trailing \" by \\" to avoid the java program :: misunderstanding the command line set _sysproperties=%_sysproperties:\"=\\"% set _ovproperties=%_ovproperties:\"=\\"% java %_sysproperties% %_ovproperties% ... -----Original Message----- From: Russ Freeman [mailto:[EMAIL PROTECTED]] Sent: Friday, May 03, 2002 11:05 AM To: 'Ant Users List' Subject: RE: Is there a limit on the java command-line? Yeah but I'm in a cmd shell not a command shell where I thought there was no limit. In actual fact I've narrowed it down even further: - It seems that java fails because I seem to have "C:\" on the end of the classpath even though I haven't added anything of the sort. I'm now wondering if my classpath is getting truncated somehow... -----Original Message----- From: Hunt, Bryan [mailto:[EMAIL PROTECTED]] Sent: 03 May 2002 16:59 To: 'Ant Users List' Subject: RE: Is there a limit on the java command-line? run command /? and if it lists envirnomental size options then you are well and truly still in the ice age/wonderfull world of MS -----Original Message----- From: Russ Freeman [mailto:[EMAIL PROTECTED]] Sent: Friday, May 03, 2002 4:50 PM To: Ant User Subject: OT: Is there a limit on the java command-line? WinXP / jdk1.3 / Ant1.5beta1 I have this java task that has started to fail by displaying its usage message. Looking deeper, it seems to be something to do with the command-line being too long. Surely those problems went with the ice age?!! --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.351 / Virus Database: 197 - Release Date: 19/04/2002 -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.351 / Virus Database: 197 - Release Date: 19/04/2002 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.351 / Virus Database: 197 - Release Date: 19/04/2002 -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
