DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15656>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15656 <java> task does not propogate classpath [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX ------- Additional Comments From [EMAIL PROTECTED] 2002-12-25 06:07 ------- I don't see this as a bug. By setting fork="false" you are running in Ant's virtual machine and therefore you see the java.class.path property of that VM. Running within Ant's VM is a convenience but it comes with limitations. These limitations relate to things like classpaths, classloader hierarchy, use of System.out, etc. If you want a clean VM with an environment the same as would exist from the command line you will need to set fork="yes" Merry Christmas -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
