Ok, that sounds reasonable to me. Although I think that the current
"client/UI centric" view will change with time. More and more RCP
applications will do client/server communication (e.g. Riena´s remote
services, p2 using ECF which uses core.net´s ProxyManager, ..).|
So, my conclusion: Not yet, may be after 3.5.
John Arthorne wrote:
Generally the RCP feature contains a
minimal subset of plugins of interest to RCP applications. Most (all?)
of the core.* plugins there are present because they are required by
UI. Typically this feature is used as a starting point for RCP apps,
other bundles from the platform can easily be added on top. For example
some RCP applications use org.eclipse.core.resources and related core
but most don't. So, those who need it just install it on top. Is there
a particular reason you think those plugins are needed in the RCP
If you still think this is important, please enter a bug report and we
can continue the discussion there.
I am wondering what the rules are
projects to become part of the Eclipse RCP SDK.
Especially I am asking for the
which are not part of it although a
lot of other core.* bundles are there.
eclipse-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit