About 1., see includeAntRuntime and includeJavaRuntime attributes , does not help remove the system classpath ..
"build.sysclasspath=ignore" should work, but could you please provide me the usage. it looks like a task property , how and where to specify the value. About 2., why would you want to do that? i have different projects to build, but the compiled classes go to same output locations. for one project i want the compile to take the compiled classes into the classpath but for the another project i want to use the jars built out of prior release to be used in the classpath ahead of the current output location classes. thanks -----Original Message----- From: Mike Dougherty [mailto:[EMAIL PROTECTED]] Sent: October 15, 2002 2:23 PM To: 'Ant Users List' Subject: RE: javac class path > -----Original Message----- > From: Dominique Devienne [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, October 15, 2002 2:14 PM > To: 'Ant Users List' > Subject: RE: javac class path > > > About 1., see includeAntRuntime and includeJavaRuntime attributes. > > About 2., why would you want to do that? --DD > > -----Original Message----- > From: Menon, Joby [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, October 15, 2002 4:09 PM > To: Ant Users List > Subject: javac class path > > 1. How can i let ant know not to use the system classpath > appended/prepended > to the classpath defined in build file via classpath attribute. > > 2. how can i let ant know not to use the destination directory > appended/prepended(to output the classes) set in the javac > target to the > classpath defined in the build file via classpath attribute. > > thanks > I would have thought using "build.sysclasspath=ignore" a better approach? Is there a reason why includeAntRuntime and includeJavaRuntime are better in this case? /mike -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
