On 1/29/2014 2:47 AM, Wim Jongman
wrote:
<stuff deleted>
Then we need to discuss the new model. I have great
experience with feature modeling but unfortunately not with
all the details of ECF so we need to sit together (virtually)
and wade through all the features. What do you say if we take
a slot next week for a couple of hours and to take a stab at
the model?.
Ok. What I would suggest though is that prior to our discussion
that you get the current contents (HEAD) of the bug409787 branch and
we can start from there. See the comments I've been adding about
changes/updates I've been making as comments on the associated bug
[1].
A quick status about that: I've pushed what I think is a reasonable
new feature structure for
a) core
b) filetransfer
c) both httpclient 3.1 and httpclient4 providers
d) ssl fragments
Getting these figured out early (and working with David Williams) is
important for our continued use for p2. Plus everything else ECF
depends upon the core bundles/feature...so that's another reason.
My plan is to begin working ASAP on any refactoring/changes to (in
this general order):
1) discovery (API, providers, dependencies, UI, etc)
2) remote services (APIs, providers, dependencies, rest, UI, etc)
3) OSGi remote services (built on both of the above, includes OSGi
code, RSA impl, examples, etc)
4) ECF on server (APIs, providers, servlet, deps, etc)
4) Everything else (presence, datashare, telephony, sync/collab,
...APIS, providers, deps, etc., examples, apps, test code, Eclipse
UI, etc)
And...we need to begin testing the build/releng for the bug409787
branch soon/asap...so that we can begin providing core+filetransfer
repos to David Williams/p2...to test the new platform integration.
Thanks,
Scott
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=409787
_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev
|