Summary: | Possibility for a corrupt feature on install | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Vlad Klicnik <klicnik> | ||||
Component: | Update (deprecated - use Eclipse>Equinox>p2) | Assignee: | Christophe Elek <celek> | ||||
Status: | RESOLVED FIXED | QA Contact: | |||||
Severity: | critical | ||||||
Priority: | P1 | ||||||
Version: | 2.0 | ||||||
Target Milestone: | 2.0 F2 | ||||||
Hardware: | PC | ||||||
OS: | Windows 2000 | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Vlad Klicnik
2002-05-22 02:42:52 EDT
We need to NOT install feature files if the feature already exists (what about checking, do we check the file system for the directory or the plugin version, b/c we can have a plugin org.plugin1 in com.company.plugin23_2.0.0 right) Then we have to check the abort and remove doesn't remove the feature files * if feature with same id & version is already on site, skip file copy * if not, check if <id>_<version>/feature.xml exists * if not .... go ahead and copy * if yes, we have an "imposter" feature living in the target directory .... CoreException Feature.install() checks if a feature with the same id_ver has been installed in the site. UpdateManagerUtils.copyToLocal throws an IO Exception if the to create already exists on the file system. Created attachment 1041 [details]
Dialog if an 'imposter feature' is installed [GIF]
SiteFileContentConsumer and SiteFilePluginContentConsumer now remember which file they installed. During an abort only these files will be deleted. Issue, the directories will stay Empty directories are removed. Fixed. Version as v20020524_16718 Fixed, 0528 |