[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[ecf-dev] provisioning of ECF 3.8.0 RS/RSA with karaf
|
Hi Folks,
In preparation for releasing ECF 3.8.0 (3/10), today 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
