[
https://issues.apache.org/jira/browse/UIMA-5798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16531891#comment-16531891
]
Marshall Schor commented on UIMA-5798:
--------------------------------------
Thank you for testing!
Re: changing the implementation: The only use case I'm aware of that calls the
Resource Manager's copy() is the setup for a PEAR within a UIMA pipeline. This
use case overrides the value of this field in the copy.
I am not in favor of changing this behavior as it makes copying either
incomplete (if the copy has uimaCL = null), or expensive (if the copy has
uimaCL = some kind of new CL impl), unless a real-world use case appears that
can guide the design choices.
> The verification of a PEAR let the files locked
> ------------------------------------------------
>
> Key: UIMA-5798
> URL: https://issues.apache.org/jira/browse/UIMA-5798
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
> Affects Versions: 2.1
> Reporter: Serge Démoulin
> Assignee: Marshall Schor
> Priority: Critical
>
> The method org.apache.uima.pear.tools.InstallationTester#doTest() create many
> new ResourceManager and the method must call ResourceManager#destroy() that
> is not the case.
> Moreover every class responsible for creating a new ResourceManager must be
> responsible for destroying it in an appropriate way.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
