Summary: | Feature without license cannot be disabled. | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Peter Manahan <manahan> |
Component: | Update (deprecated - use Eclipse>Equinox>p2) | Assignee: | Dejan Glozic <dejan> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | blocker | ||
Priority: | P1 | CC: | greg_adams, patmc |
Version: | 2.0 | ||
Target Milestone: | 2.0.1 | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
Peter Manahan
2002-06-23 20:39:20 EDT
The current rule seems to be that features with no license cannot be updated. However it still gets loaded. When this occurs it can not be updated or disabled via eclipse. It needs to be removed manually. Because the features some products ship may ship without licenses (the license is accepted at install time) This means that the product would not be updateable. What should occur is that the feature being "downloaded" from the update site have a license for click through. We have up'd the severity of this. To be clear, only root features can be disabled. So the license would only have to be in the root feature. That said, it is confusing to be blocked by license text that is only visible during the act of an update (the accept/reject question). The update manager only seems to be able to show license content from the identified html reference and not the text in feature.properties (unless in the update wizard). The point is the presence/absence of license cannot be a blocking factor. Should not prevent Enable/Disable if a feature without a license has already been installed. The problem in code is that absence of license causes the 'do' button to be hidden irrespective to the feature context. The correct fix would be to test the license presence only for features that are not in the local site context (i.e. already present in the current configuration). Fixed in 2.0.1 stream |