Return-Path: Delivered-To: apmail-jakarta-ant-user-archive@apache.org Received: (qmail 62642 invoked from network); 17 Jul 2002 23:36:46 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 17 Jul 2002 23:36:46 -0000 Received: (qmail 3185 invoked by uid 97); 17 Jul 2002 23:36:55 -0000 Delivered-To: qmlist-jakarta-archive-ant-user@jakarta.apache.org Received: (qmail 3093 invoked by uid 97); 17 Jul 2002 23:36:55 -0000 Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Users List" Reply-To: "Ant Users List" Delivered-To: mailing list ant-user@jakarta.apache.org Received: (qmail 3015 invoked by uid 98); 17 Jul 2002 23:36:54 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Message-ID: From: John Lindwall To: 'Ant Users List' Subject: RE: javac task: Spaces in dir name MORE INFO Date: Wed, 17 Jul 2002 16:33:02 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C22DEA.4B3F9310" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N ------_=_NextPart_001_01C22DEA.4B3F9310 Content-Type: text/plain; charset="iso-8859-1" Thanks for setting me straight. That jikes-named file is quite confusing. What I lose by not forking is the ability to set the javac memory-size -- this is a big compile job and it needs more then the default (200m in my case). So it sounds like this is a problem with the fork capability of the javac task. Ug. I know that dirs with spaces in them ar ea pain and I do try to avoid them. But they are valid and I wish ant supported them. Thanks! John > -----Original Message----- > From: Diane Holt [mailto:holtdl@yahoo.com] > Sent: Wednesday, July 17, 2002 4:18 PM > To: Ant Users List > Subject: RE: javac task: Spaces in dir name MORE INFO > > > --- John Lindwall wrote: > > It does work if I say "fork="false". I _think_ I am using > jikes when I > > say fork="true" because the -debug output showed a weird -g > option that > > specifies a jikes temporary file. > > The -g flag has to do with compiling with debug. The jikes-* > file is an > @file that holds the names of the files to compile when they're too > numerous to fit on a command line -- the fact that its name > starts with > "jikes" is just historical (and should really get changed so > we don't have > to explain that all the time). > > > I'm very confused over why jikes would be used actually -- our > > build.compiler property is set to "modern". > > You're not running 'jikes' (see above). When you set > 'fork="true"', you > won't in fact be running whatever the compiler you specified for > build.compiler, because with 'fork', that gets ignored (verbose output > will say something like "Since we're forking, build.compiler setting > ignored."). > > > Maybe if I could do fork="true" and use the normal JDK > javac I'd be in > > good shape? > > No, what you want to do is not fork, since you said that does > work for the > path problem, and since you're setting build.compiler > (although you don't > actually need to, if you're running JDK1.3 or 1.4). > > Diane > > ===== > (holtdl@yahoo.com) > > > > __________________________________________________ > Do You Yahoo!? > Yahoo! Autos - Get free new car price quotes > http://autos.yahoo.com > > -- > To unsubscribe, e-mail: > > For additional commands, e-mail: > > ------_=_NextPart_001_01C22DEA.4B3F9310--