http://nagoya.apache.org/bugzilla/show_bug.cgi?id=630
*** shadow/630 Fri Feb 16 14:27:26 2001 --- shadow/630.tmp.29479 Sun Feb 18 05:46:22 2001 *************** *** 2,9 **** | Class loader for <java> with specified classpath incorrectly uses system c | +----------------------------------------------------------------------------+ | Bug #: 630 Product: Ant | ! | Status: NEW Version: 1.3 Beta 2 | ! | Resolution: Platform: All | | Severity: Major OS/Version: All | | Priority: Medium Component: Core tasks | +----------------------------------------------------------------------------+ --- 2,9 ---- | Class loader for <java> with specified classpath incorrectly uses system c | +----------------------------------------------------------------------------+ | Bug #: 630 Product: Ant | ! | Status: RESOLVED Version: 1.3 Beta 2 | ! | Resolution: FIXED Platform: All | | Severity: Major OS/Version: All | | Priority: Medium Component: Core tasks | +----------------------------------------------------------------------------+ *************** *** 131,134 **** Using the other constructor (which defaults systemFirst to true) means that some classes may be loaded by the system class loader, and some by the classpath ! specified in build.xml. --- 131,150 ---- Using the other constructor (which defaults systemFirst to true) means that some classes may be loaded by the system class loader, and some by the classpath ! specified in build.xml. ! ! ------- Additional Comments From [EMAIL PROTECTED] 2001-02-18 05:46 ------- ! I have made this change but I have gone a little further and added the ! concept of isolating the classloaders. Now if the class isn't found in the ! supplied classpath, it will throw a classNotFoundException even if the ! class is avilable on the system classpath. This makes the <java> task work much ! like running java from the command line (but not identical). So, it now ! works like this ! 1. If you don't supply a classpath, Ant's classpath is used ! 2. If you do supply a classpath, all necessary classes need to be ! on that classpath. ! ! If you always want to include the system classpath in all classpaths, ! you can set the property ! build.sysclasspath to eiher "first" or "last" depending on where you want the ! system classpath to appear.
