Summary: | Features without corresponding plugin cannot be referenced | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Greg Adams <greg_adams> |
Component: | Update (deprecated - use Eclipse>Equinox>p2) | Assignee: | Dejan Glozic <dejan> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | major | ||
Priority: | P2 | ||
Version: | 2.0 | ||
Target Milestone: | 2.0.2 | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
Greg Adams
2002-07-08 22:29:04 EDT
Hum , we may not be clear. I can see the includes tag seems to require a feature id, but the requires tag needs a plugin id. We should make it clearer that include is for feature nesting, while requires is for plugin dependency. So, in a nutshell, you should be able, in the current spec, to include a feature that doesn't have a plugin. the require tag takes a plugin id and is not used for nesting... Move to p3 as specified, change spec Investigate if it is doable to add an attribute 'feature' in the 'import' element in requires to allow feature prereq instead of plug-in prereq. Attribute feature has been added. test Core is now supporting 'feature' in 'import' elements, Update UI modified to handle it. Implemented - needs testing. Fixed. |