|Why example plugins are required to use ECF? [message #619774]
||Sun, 28 October 2007 22:20
Originally posted by: hiroki.kondo.change-vision.com|
I think JoinGroupWizardAction and SelectProviderAction sholud be
included in ECF core feature.Why JoinGroupWizardAction and
SelectProviderAction are included in example Plug-in?
Example Plug-ins are reference implementation,isn't it?
So, It is not necessary to use ECF Feature.
And I look forward to use necessary Actions to use ECF.
I found these Action. These Actions are nessesary to use
ECF Communication Perspective.
I want to these Actions are included in ECF Core Features,
and I want to delete unnecessary Feature to use ECF, for example,
Robot Plugin, that is sample implementation to develop on ECF.
|Re: Why example plugins are required to use ECF? [message #619791 is a reply to message #619789]
||Wed, 31 October 2007 07:51
Originally posted by: mkuppe.versant.com|
Remy Chi Jian Suen wrote:
> If you have comments about how we should structure our features, please
> bring it up on the ecf-dev mailing list and/or open a bug.
Let me quote Scott on ECF features in another bug...
> Doing *this* feature refactoring is a bigger (but still
> desireable/necessary) thing...but this also has some interactions with the
> Equinox Provisioning work for 3.4. That is, the Equinox provisioning work will
> obsolete the Eclipse 'features' and so it might make more sense to focus on
> using the new provisioning work to create an set of ECF 'installable units'
> (concept from Equinox provisioning). 
So please fill bug reports, but be warned that we might have no chance
to fix it before we switch to IUs.
Powered by FUDForum
. Page generated in 0.01660 seconds