[UIMA-4064] DUCC CLI: use a class loader to keep user's classpath and DUCC's use of 3rd party software segregated.

• Type: Task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.1.0-Ducc
• Fix Version/s: 2.0.0-Ducc
• Component/s: DUCC
• Assignee: Jim Challenger
• Reporter: Jim Challenger
• Created: 27/Oct/14 16:55
• Updated: 26/Mar/15 19:51
• Resolved: 26/Mar/15 19:51

Description

The most common use of the CLI is by calling its main() from within Eclipse, with the user's application classpath. If the classpath contains pointers to 3rd party packages used by the CLI, and comes before uima-ducc-cli.jar, the CLI can malfunction.

Similarly, uima-ducc-cli.jar is often left in the classpath for other than DUCC CLI usage, and it's own use of 3rd party packages can interfere with applications.

To remedy this we remove as much 3rd party usage as possible, and use a classloader for the rest to provide 2-way protection.