[UIMA-496] PEAR API does not delete the PEAR ID subdirectory before the new content is installed

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.2
• Component/s: Core Java Framework
• Assignee: Adam P. Lally
• Reporter: Michael Baessler
• Created: 12/Jul/07 08:22
• Updated: 05/Nov/09 10:44
• Resolved: 12/Jul/07 14:06

Description

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.

Issue Links

• is related to: UIMA-1652 Cannot hot-install a PEAR twice