Summary: | Common children feature will be removed | ||
---|---|---|---|
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: | major | ||
Priority: | P2 | CC: | tim_koss |
Version: | 2.0 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
Christophe Elek
2002-05-28 06:12:46 EDT
ConfigurationPolicy#unconfigure(IFeatureReference) checks the Feature doesn't have a configured parent, otherwise it does not unconfigure the feature and set the Activity to NOK. This will work for nested feature is we unconfigure teh parent feature before the children (which is the case). The method ConfigurationPolicy#validateNoConfgiuredParents returns true if teh Feature doesn't have a configured parent Tested with 2 nested feature with same child, The child feature is not disable when on parent is disable. Also fixed a FeatureReference comparison bug. Feature#featureAlreadyInstalled now compares Version and Identifier instead of URL Version in v20020529H1715_18021 Fixed issue where the computation of already existing feature was based on URL, which didn't work to find if a remote feature was already installed on the local site. This was resultng in not beeing able to install a children feature. The error message stated the file 'feature.xml' already existed Fixed in Latest version *** Bug 18260 has been marked as a duplicate of this bug. *** Verified 0531 |