Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 331043

Summary: Add artifact to Target Platform behaviour oddities
Product: [Eclipse Project] PDE Reporter: Jeff McAffer <jeffmcaffer>
Component: UIAssignee: PDE-UI-Inbox <pde-ui-inbox>
Status: RESOLVED WORKSFORME QA Contact:
Severity: normal    
Priority: P3 CC: caniszczyk
Version: 3.7   
Target Milestone: ---   
Hardware: PC   
OS: Mac OS X - Carbon (unsup.)   
Whiteboard: stalebug

Description Jeff McAffer CLA 2010-11-24 12:04:44 EST 
The FilteredIUSelectionDialog and TargetRepositorySearchHandler provide a very useful function allowing the user to search for things known in the p2 metadata and add the corresponding IUs to their target definition.  However, the implementation seems to simply create a new IUBundleContainer for every set of elements added.  Users using this feature often will end up with unmanagable target defintions and no way of merging the containers.

Another issue is that the discovered IUs are added directly to the IU container.  The container's design expects that these IUs represent features. While the API may not reflect it, that implicit expectation may show up in nasty ways.  To be clear, I'd like the IUBundleContainer to be able to hold any kind of IU.  We just need to check that the code paths work right when IUs added are not features.

Related to this is the question of what repositories to use when resolving the given container.  Currently the container repo list is set to null meaning all available repos.  This may be ok.  Have to think on that.
Comment 1 Jeff McAffer CLA 2010-11-24 12:07:08 EST 
one other thing...  The handler creates a new container and slams the settings to use the slicer.  This may be at odds with the other containers in the target.  Currently there is a restriction that all containers have the same setting for slicer vs planner.
Comment 2 Eclipse Genie CLA 2018-10-30 00:04:19 EDT 
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.

--
The automated Eclipse Genie.
Comment 3 Lars Vogel CLA 2019-09-02 14:59:08 EDT 
This bug has been marked as stalebug a while ago without any further interaction.

If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard flag.
Comment 4 Lars Vogel CLA 2019-09-02 15:12:53 EDT 
This bug was marked as stalebug a while ago. Marking as worksforme.

If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard tag.