Return-Path: Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list ant-user@jakarta.apache.org Received: (qmail 59780 invoked from network); 31 Oct 2000 01:39:22 -0000 Received: from gkca-public.discoverbrokerage.com (HELO gkca.discoverbrokerage.com) (63.85.63.20) by locus.apache.org with SMTP; 31 Oct 2000 01:39:22 -0000 Received: by gkca.discoverbrokerage.com; id RAA01627; Mon, 30 Oct 2000 17:38:52 -0800 Received: from seal.discoverbrokerage.com(204.242.31.83) by gkca.discoverbrokerage.com via smap (V5.5) id xma001606; Mon, 30 Oct 00 17:38:44 -0800 Received: from bayexch.discoverbrokerage.com (bayexch1.discoverbrokerage.com [10.2.200.20]); by seal.discoverbrokerage.com with ESMTP id RAA28577 for ; Mon, 30 Oct 2000 17:38:43 -0800 (PST) Received: by bayexch1.discoverbrokerage.com with Internet Mail Service (5.5.2650.21) id ; Mon, 30 Oct 2000 17:38:44 -0800 Message-ID: <13356BB49A60D311A446009027B0F4670166D046@bayexch2.discoverbrokerage.com> From: "Ventimiglia, David" To: "'ant-user@jakarta.apache.org'" Subject: RE: javac task and classpath attribute Date: Mon, 30 Oct 2000 17:38:43 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N It looks like elements only get added to the classpath if they exist. For instance, in Dave's example below, if "foo" doesn't refer to a real file or directory off of the project base path, then he won't see it in the messages emitted when he runs Ant. In my case, it looks like property values aren't getting evaluated properly by the time the classpath is evaluated, so the Javac task checks to see if things like these exist: ${WL_HOME}\classes\boot ${WL_HOME}\eval\cloudscape\lib\cloudscape.jar Where ${WL_HOME} is being treated literally, rather than having its value, c:\weblogic, substituted. Of course these paths don't exist, so it gets left off the classpath, leading to compilation errors. The only way I can seem to get it to work is to either remove the property references, or to set a system classpath (for example, by running $WL_HOME\setEnv.cmd) before running Ant. The question is, why aren't my properties being evaluated? I must be missing something fundamental. Any ideas? Here's a copy of my build.xml file: .... set some other properties .... .... some other targets .... -----Original Message----- From: Dave Inskeep [mailto:dave.inskeep@bea.com] Sent: Tuesday, October 24, 2000 8:54 AM To: ant-user@jakarta.apache.org Subject: javac task and classpath attribute Does anyone else have problems with using the classpath attribute, classpath nested element, or classpathref attribute with the javac task? No matter what I try, javac seems to ignore the classpath and use what ant ran with. In desperation I even just tried: hoping to see my classpath as foo. However, this is what I get with "ant -verbose": [javac] Compilation args: jikes -d C:\Projects\beast\classes -classpath "C:\Program Files\JavaSoft\JRE\1.2\lib\ext\iiimp.jar;C:\Projects\beast\classes;C:\java\a nt\lib\ant.jar;C:\java\ant\lib\jaxp.jar;C:\java\ant\lib\parser.jar;C:\java\j dk1.2.2\lib\tools.jar;C:\Program Files\JavaSoft\JRE\1.2\lib\rt.jar;C:\Projects\beast\src" It appears to be just the classpath that the ant batch file uses plus my srcdir and destdir. Am I missing something obvious? I'm using version ant 1.2. Thanks, Dave