Summary: | Subclass of JUnitTask that manages classpath dependencies according to directory tree | ||
---|---|---|---|
Product: | Ant | Reporter: | Ben Yu <ajoo.email> |
Component: | Optional Tasks | Assignee: | Ant Notifications List <notifications> |
Status: | NEW --- | ||
Severity: | enhancement | Keywords: | PatchAvailable |
Priority: | P2 | ||
Version: | 1.6.5 | ||
Target Milestone: | --- | ||
Hardware: | Other | ||
OS: | other | ||
Attachments: |
The core tree class loader. No dependency on Ant API.
org.codehaus.classloader.TreeClassLoaders is the facade class to create tree classloaders.
the JUnitTask subclass that provide tree classloader support for forked mode |
Description
Ben Yu
2006-08-11 19:48:43 UTC
Created attachment 18701 [details]
The core tree class loader. No dependency on Ant API.
org.codehaus.classloader.TreeClassLoaders is the facade class to create tree classloaders.
This package contains a tree class loader implementation. (optionally support
hot-swap).
Run "ant doc" to generate javadoc.
Created attachment 18702 [details]
the JUnitTask subclass that provide tree classloader support for forked mode
This package has the actual task class that calls tree-classloader to manage
dependency using directory tree.
org.codehaus.neptune.ant.tasks.JUnitTask is the subclass.
Usage: Load this class as a task (call it junit2 for example), then use the
same syntax as <junit>, except now the jar files in each directory in the
classpath are loaded and managed following directory tree structure.
I have the feeling that if I understood this any better I could see how the tree ClassLoader could be generally useful on its own. As it is I didn't entirely understand it. For one thing, if I DL and build the tree classloader attachment, its tests don't run successfully. :( |