[
https://issues.apache.org/jira/browse/UIMA-496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12512010
]
Michael Baessler commented on UIMA-496:
---------------------------------------
To fix this issue, I will clean the target installation directory before the
new PEAR file is installed to it. If the target install directory should be
cleaned can be specified with an additional parameter when using the
InstallController PEAR API. The default will be to clean the directory.
An known issue with that approach is, that after installing a PEAR file to a
directory, the same PEAR file cannot be installed again to the same directory
with the same JVM since the JVM has locked the jars so they cannot be deleted
when the directory for the next installation should be cleaned. To do that, the
JVM must be restarted, or another installation directory must be used. The JVM
locks the jar files when the installation verification is executed.
> PEAR API does not delete the PEAR ID subdirectory before the new content is
> installed
> -------------------------------------------------------------------------------------
>
> Key: UIMA-496
> URL: https://issues.apache.org/jira/browse/UIMA-496
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
> Reporter: Michael Baessler
> Assignee: Michael Baessler
> Fix For: 2.2
>
>
> When installing a PEAR file, currently the InstallationController API
> overrides all available data in the target installation directory. The
> directory content isn't removed before. So it can happen that old class files
> or descriptor files that are never valid are still in the installation
> directory since they will not be removed when the new stuff is installed.
> Existing files with the same name will be overridden.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
