Summary: | Deleting non-optional features from file system throws error | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Christophe Elek <celek> |
Component: | Update (deprecated - use Eclipse>Equinox>p2) | Assignee: | Christophe Elek <celek> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P2 | ||
Version: | 2.0 | ||
Target Milestone: | 2.0.2 | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
Christophe Elek
2002-08-23 18:22:44 EDT
We should not be blank because of one feature. Christophe, please take a look at this. I deleted XYZBogus feature and that is causing SiteManager.getLocalSite() to throw core exception. Without local site, I cannot drill down and show install sites etc. If one feature is missing, you should still return ILocalSite, particularly since we have handles to delay resolving features (IFeatureReference). ConfigurationView cannot be made more robust because its content provides chokes at the very beginning (when asking for ILocalSite instance). BTW, not only that configuration view is unusable, but anything else in the UM is broken whenever the UI needs to consult local site to compute something. The trace of this issue looks like the trace of bug 23853. In both cases, an error is thrown in 2.0.1 when a feature referenced by another is missing. The new implemented code in 2.0.2 'eats' the error. Test that the fix for 23853 also fixes this issue. Verified the fix also fixes this issue. Installed Root 1.0.0, removed XYZBOGUS feature Eclipse starts ok and no error is thrown Root 1.0.0 appears as broken feature XYZ and Bogus optional child feaure appear as root feature Nothing in .log is not started with -debug and options. |