[
https://issues.apache.org/jira/browse/UIMA-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Challenger closed UIMA-4064.
--------------------------------
Resolution: Fixed
> DUCC CLI: use a class loader to keep user's classpath and DUCC's use of 3rd
> party software segregated.
> ------------------------------------------------------------------------------------------------------
>
> Key: UIMA-4064
> URL: https://issues.apache.org/jira/browse/UIMA-4064
> Project: UIMA
> Issue Type: Task
> Components: DUCC
> Affects Versions: 1.1.0-Ducc
> Reporter: Jim Challenger
> Assignee: Jim Challenger
> Fix For: 2.0.0-Ducc
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
