Re: [ecf-dev] provisioning of ECF RS/RSA with karaf

[Scott Lewis <slewis@xxxxxxxxxxxxx>]

Hi Wim and all,

On 3/8/2014 2:30 AM, Wim Jongman wrote:

Why not add the o.e.e.remoteservice.sdk,feature to the category.xml? It will be visible in our current download site.

I've decided to go way beyond that :).  

First...just to be clear...there is a category for the equivalent of the remoteservice SDK in the category.xml...it's called:  ECF OSGi Remote Services/Remote Service Admin SDK.   It has the SDK itself, RS examples, and source.

I've also added a new Jenkins o.e.e.remoteservice.sdk project to the build [1].

I've slightly modified the karaf-features.xml generating shell script to create karaf-features.xml that are compliant with the more Karaf version 3 [2].

And now the 'big one'...I've created and tested a completely new karaf-features.xml that simplifies the install of the ECF RS SDK (and examples) into Karaf 3.0.  I've committed this here [3].

My intention for 3.8.0 (Monday) is to hand edit this new karaf-features-rssdk.xml and put it in place of karaf-features.xml at the ECF SDK level on download.eclipse.org once the final release build is done (on Sunday eve pacific time).  I've done a test/staging build this Sat am, and am running a test install of the Karaf ecf.rs.sdk feature into a test Karaf 3 instance right now.   I expect it will work as Friday I've gone through a full install, test, running RS Timeservice Host many times :).

For after 3.8.0 release, I've opened a releng bug to automate the creating/template filtering of this new, more karaf-consumable structure [5].

I'll be working on some changes/additions to the ECF download page, as well as wiki pages...describing how to install the ECF RS SDK into Karaf 3.0 during today/Sat and Sunday.

Things for others todo in prep for 3.8.0 release

1) Work on the New and Noteworthy (i.e. adding the items that are in the slides in the N&N html template [4])
2) Test the ECF p2 install against 4.4M6 and/or Kepler SR 2.   The most recent test/staging repo is here [6].
3) Test usage of karaf features (on Karaf 3.0) as described...and document the Karaf-based install and remote service (Timeservice) test process in wiki.

Scott

[1] http://build.ecf-project.org/repo/C-HEAD-remoteservice.sdk.feature/lastSuccessful/archive/site.p2/
[2] http://karaf.apache.org/manual/latest/users-guide/provisioning.html
[3] http://git.eclipse.org/c/ecf/org.eclipse.ecf.git/tree/releng/org.eclipse.ecf.releng.bm/karaf/templates/rssdk
[4] http://git.eclipse.org/c/ecf/ecf.git/tree/NewAndNoteworthy_3.8.0.html
[5] https://bugs.eclipse.org/bugs/show_bug.cgi?id=429939
[6] http://build.ecf-project.org/repo/C-HEAD-remoteservice.sdk.feature/lastSuccessful/archive/site.p2/

cheers,

Wim

On Fri, Mar 7, 2014 at 7:39 PM, Scott Lewis <slewis@xxxxxxxxxxxxx> wrote:

Hi Folks,

In preparation for releasing ECF 3.8.0 (3/10), yesterday I tested the install of the latest build into Apache Karaf v3.0.0 [1].

Currently, we build the entire ECF SDK and create a deployment repo.   The SDK feature and repo includes ECF's OSGi Remote Services/RSA implementation, and all the other parts of ECF (e.g. docshare, presence API, Eclipse UI and collab, etc).    It also includes all the generated source bundles.

As part of the build of the SDK feature, an associated karaf-features.xml is created [2].   This karaf-features.xml contains, by default, all of the bundles/plugins for the SDK itself...i.e. all the RS/RSA SDK, all the Eclipse-based plugins, and all of the generated source bundles.

What this means is that if karaf users install everything in the SDK feature/karaf-features.xml (which is the natural thing to do), they will get much more than the RS/RSA impl...they will get all the Eclipse plugins, and the generated source bundles.

I would like to make it easier for karaf users to get only the RS/RSA impl (and possibly examples)...without getting all the Eclipse plugins (i.e. docshare, UI, etc.)...that aren't relevant to karaf users...and won't, in fact, be able to actually run (because they depend upon parts of Eclipse that don't exist in karaf-based runtimes).

Some possibilities for making install of RS/RSA into karaf frameworks:

A) One would be to just remove the irrelevant plugins/bundles from the SDK feature/karaf-features.xml...and only include the RS/RSA bundles, RS examples, and source code (perhaps not the source code bundles?).    I'm not sure of the best way to do this...either Markus or Wim will probably have to advise as I think it would mean modifying our build template in some manner include only a subset of the SDK feature bundles into the karaf-features.xml.

B) Another way would be to create a new build project...that builds this feature: org.eclipse.ecf.remoteservice.sdk.feature.   Then we can/could deploy the repo created via this new build to download.eclipse.org *in addition* to the SDK.   Then karaf users could simply point to the location of this repo and install only the RS SDK.   This is a slightly worse option, IMHO, because it means having/maintaining two separate repos once released...and that's got some possibily undesirable side effects.

Any other options that people can think of.?..i.e. to simplify provisioning for karaf users that want to use ECF's RS/RSA impl?

Without any further input I'm inclined to go with 'A' in the short term (i.e. for ECF 3.8.0).  Further...once this gets done (on Friday), I will create a wiki page describing how to install ECF's RS/RSA impl via karaf, so that the methods are clear for people.

Thanks,

Scott

[1] http://karaf.apache.org/
[2] http://build.ecf-project.org/repo/C-HEAD-sdk.feature/lastSuccessful/archive/site.p2/karaf-features.xml


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

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