Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 361222 - [publisher] Provide methods to get actually included features/bundles in IProductDescriptor
Summary: [publisher] Provide methods to get actually included features/bundles in IPro...
Status: CLOSED WONTFIX
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: p2 (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: P2 Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks: 361215
  Show dependency tree
 
Reported: 2011-10-18 04:49 EDT by Tobias Oberlies CLA
Modified: 2019-11-14 03:53 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tobias Oberlies CLA 2011-10-18 04:49:24 EDT
Currently, the IProductDescriptor only offers methods which work on the syntactical level of product files, i.e. getFeatures() returns the list of features in the product file regardless of whether these features are actually _contained_ in the product or not. This requires all users to re-implement the implications of useFeatures and the new 'type' attribute (see bug 325622). This is more complicated than necessary.

The IProductDescriptor interface should be extended to also offer methods on the semantical level, e.g. getContentBundles() and getContentFeatures(), which hide the useFeatures/type attributes. This should probably be sufficient for all users, so I would even go as far as deprecating the syntactic methods.
Comment 1 Lars Vogel CLA 2019-11-14 03:53:56 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.