Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 232843 - [reconciler] Determining /specifying the install roots from dropins and links
Summary: [reconciler] Determining /specifying the install roots from dropins and links
Status: RESOLVED WONTFIX
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: p2 (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows XP
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: P2 Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-19 14:35 EDT by Susan McCourt CLA
Modified: 2020-02-21 00:50 EST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Susan McCourt CLA 2008-05-19 14:35:04 EDT
From bug #224472
In my case, all the add-on features are brought in through *.link files
pointing to various pre-existing extension locations, and what P2 does is mark
each and every feature it finds therein as an install root.

I think that in case some features are brought in by a method like dropins/ or
links/ which does not involve the user manually selecting something to install,
P2 should be smart enough to mark exactly those features as install roots that
are roots, i.e. that are not included as sub-feature within any other feature
on the features currently being added.

In my opinion, the missing categorization for stuff being brought in via links/
is a bug, which actually renders the view unusable, and not an enhancement
request.

In our commercial offering which is comprised of lots of features and plugins,
we're currently also using *.link files to compose the entire installation
(though that may change). How can we tag (or untag) something as install root
in our custom Eclipse Product?

It looks like my problem is actually a bit different than the original
description on this bug, in that I'm experiencing exactly the opposite problem
of what the original submitter saw (too many features and not too few).
Comment 1 Pascal Rapicault CLA 2009-08-25 13:39:04 EDT
I agree with the annoyance, but dropins should not be used to install large amount of plug-ins or complete products. If people are looking for a clean way of installing things, then I would suggest addressing bug #225344. Then maybe there we will come up with something that can be reused in this context.
Comment 2 Eclipse Webmaster CLA 2019-09-06 16:11:57 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.
Comment 3 Ed Merks CLA 2020-02-21 00:50:53 EST
It's not clear to which view this problem applies.