Re: [ecf-dev] feature refactoring progress

[Wim Jongman <wim.jongman@xxxxxxxxx>]

Scott, I am looking at the repo and I have some questions/remarks:

The term "Target Components": What does "Target" mean? It has always confused me because "Target" in communications generally means "the other system".

The "ECF Target components for Eclipse", is that the SDK? If it is, I suggest to rename it.  

In the "Details" it says that it also includes the examples but I believe you have removed them.

The filetransfer SSL features are now in the uncategorized category. I would expect it in the file transfer category

"ECF Remote Services Target Components" is this the Remote Services SDK? If not I suggest to drop the word "Target" 

The "ECF Remote Services SDK Examples" is in uncategorized. I would expect it in the remote services category.

It makes no sense to install the ECF Core and core SSL features. Do they need to be listed here? I guess the site must list all features that are not included to the answer is probably yes.

I don't see the standalone docshare function you describe.

Cheers,

Wim

On Sun, Feb 9, 2014 at 5:57 PM, <slewis@xxxxxxxxxxxxx> wrote:

Hi Folks,

I've been working on the feature refactoring [1], and I wanted to give a
status...and request your help in testing for deployment in ECF 3.8 (early
March).

Status

1) I've completed the core and filetransfer refactoring (for use by
Equinox/p2/Platform), and help of with Platform releng this should
eliminate many of the install problems ECF consumers have experienced in
the past.  See bug comments e.g. [2] for details.

2) I've refactored many of the ECF features...such that almost all of them
use requires rather than includes for looser coupling.

3) I've removed the remote service examples features [3] from the remote
service sdk (all in one), and created a new feature:
org.eclipse.ecf.remoteservice.sdk.examples.feature that has the examples.
 This will make it possible for consumers to install the remoteservice
sdk/all-in-one without the examples.   Of course if they wish to install
the examples they can do so directly with this new feature.

4) I've created a feature just for docshare
(org.eclipse.ecf.docshare.feature), which will allow consumers to install
just docshare into Eclipse.  This in response to one of the requests on
this mailing list.

5) I've adjusted test code and the builder to build everything with new
structure.   There is more to do here, but it's now stable.

Request

I would like assistance on testing out this feature structure under
different install scenarios...different versions of Eclipse, different
target frameworks (Eclipse, Equinox only, servers, Felix), different user
selections of what to install (remote services only, examples,
other/Eclipse plugins, etc) .

If you are able/willing to do some of this testing, please communicate on
the bug about what scenarios you will test, so that I/others don't
overlap.  If you find problems, please open a bug and make 409787
dependent upon the new bug.

A new p2 repo is here [4].  Please use this for testing.

Thanks,

Scott

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=409787
[2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=409787#c69
[3] https://bugs.eclipse.org/bugs/show_bug.cgi?id=420931
[4]
http://build.ecf-project.org/repo/C-HEAD-sdk.feature/lastSuccessful/archive/site.p2/


_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev