> I met a very strange problem that one jar doesn't become useful after I > put it to Ant classpath setting, ClassNotFoundException will be thrown > out. After I put the jar to system's CLASSPATH, Ant target runs without > problem. [...] > Here is the sample classpath declaration in my build script. Class > com.foo.task.MyTask extends org.apache.tools.ant.Task, it is included > in 1-1.jar. The ClassNotFound class is located in 2-1.jar which will be > invoked by the class in 3-1.jar.
How so invoked? Is that class that's not found used directory by the code, or indirectly thru a Class.forName() call? If the later, you may need to use the Context ClassLoader to correctly locate the class (see overloaded form of forName()). Could be something else too, but it's not easy to diagnose with the information you provided. Class loading issues are tricky. --DD --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
