|Dropins, target platform and features [message #557393]
||Tue, 07 September 2010 09:00
| Daniel KrÃ¼gler
Registered: July 2009
The dropin folder is a very useful feature to add functionality to|
the Eclipse IDE without need to modify the Eclipse installation
directly. It is possible to add a simple link file to the dropin
folder that points to another directory containing plugins and features.
The plugins provided this way are available during the work with Eclipse
and even when starting RCP applications, which is fine.
But I notice now, that any *features* that I provided by this
approach are *not* available when e.g. attempting to add referenced
features to a feature.xml.
I'm using Eclipse 3.5.2 and wonder whether this is a known defect
or not? While trying to understand the root of the problems it seems
as if the actual target platform of a workspace is only composed by
*plugins*, and no features, which gives a first hint why there is
something going wrong. So, let me ask my question differently:
Why are features not also components of the target platform?
If that is no good idea: How can I make the features available
within Eclipse that are contributed by dropins?
Thanks for your help,
Powered by FUDForum
. Page generated in 0.01518 seconds