Hello Christian,
On 6/16/2014 10:54 PM, Christian Schneider wrote:
Hi Scott,
I see a lot of potential for ECF, also inside karaf. What makes it a
bit awkward to work with is that ECF and its dependencies are
currently not deployed to maven central.
Do you see any chances to deploy a karaf feature file and the jars to
maven central?
It's possible. Our build already produces a maven repo as well as a p2
repo. There is some work needed to automate the karaf features
construction, however [2].
It is already quite nice that ECF provides a karaf feature now but the
features refer to dependencies using http which makes it harder to run
this in an environment where you have no internet connect.
|In case of maven dependencies the standard aproach there is to have a
company maven repository that contains the artifacts. This is much
harder with hard coded http links that refer to an external server.
I'm not sure if I would refer to a maven repository as 'standard', but I
understand what you are saying.
There's some amount of repeating work necessary to publish and properly
maintain bundles at maven central. I would be happy to do so in order
to make them more easily accessible in maven environments, but speaking
plainly the ECF team needs either additional committers or new
contributions to take on new repeating releng tasks. Please consider
offering such contributions via the ecf-dev mailing list [1].
Scott
[1] https://dev.eclipse.org/mailman/listinfo/ecf-dev
[2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=430144
https://bugs.eclipse.org/bugs/show_bug.cgi?id=429939
Best regards
Christian
Am 16.06.2014 21:36, schrieb Scott Lewis:
For everyone's information,
Since the OSGi 4.3 specification, what was called Distributed OSGi
(originally as part of RFC 119) is now two chapters of the OSGi
Enterprise spec [1]. The two chapters are
1) Remote Services (chapter 100)
2) Remote Service Admin (chapter 122)
Chapter 100 introduces a set of standardized service properties that
define when and how a service is exported for remote access, while
chapter 122 introduces a modular management agent, a provider
architecture for discovery and distribution, and APIs for controlling
and monitoring RS discovery and distribution. With the R6
specification (not yet released/complete) the RSA spec has been
enhanced in several ways and the specification version has moved from
1.0 to 1.1.
Since earlier in 2014, ECF has made it's implementation of RS/RSA
available as a small set of Karaf features [2]. Next week, ECF will
have it's 3.8.1/Luna release to make available our latest impl of
RS/RSA [3]. The ECF implementation is CT-tested and fully compliant
with OSGi R5 (latest release of spec), and runs just fine on Felix,
Equinox, or other compliant frameworks.
Further, ECF RS/RSA provides an open, extensible implementation that
allows remote service developers to use one of several providers, or
if they prefer they may implement and substitute their own discovery
and distribution subsystems (e.g. based upon CXF, Cellar, JMS, MQTT,
JAX-RS, and/or proprietary discovery or distribution impls, etc).
Thanks,
Scott
[1] http://www.osgi.org/Specifications/HomePage
[2] https://wiki.eclipse.org/EIG:Install_into_Apache_Karaf
[3] https://www.eclipse.org/ecf/NewAndNoteworthy.html
[4] https://wiki.eclipse.org/ECF#OSGi_Remote_Services
