On Wed, 3 Apr 2002 20:58, [EMAIL PROTECTED] wrote: > * Use multi-parent ClassLoaders for antlibs and extensions, so that each > extension jar is loaded by a single ClassLoader in the hierarchy. > Allows classes from extensions to be shared across dependent antlibs and > extensions.
ooer! > * Changed contract of ClassLoaderManager.createClassLoader( File[] ), so > that it creates a new ClassLoader each time it is called. yay! > * Added a few test cases for DefaultClassLoaderManager. BTW I noticed that you create testdata every time through in a few cases. Is there anyreason why you don't check the binary test data into the repository? This would improve our build times and it also gets a much more reliable test set. Because we no longer have to worry about ourselves buggering up one of the ant tasks or something and this task (which is subsequently used to build test data) would then cause other uni tests to fail. If we use a known quantity then it is much easier to reliably do unit testing? Thoughts? -- Cheers, Pete *------------------------------------------------------* | "Computers are useless. They can only give you | | answers." - Pablo Picasso | *------------------------------------------------------* -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
